Cloud Manager 2.5 Support Pack 1 Patch Update 1 (2.5.1 Patch 1) resolves several issues for Cloud Manager 2.5.1. It also includes hotfixes for the Orchestration Server 3.5.1 component that have been provided since the Cloud Manager 2.5.1 release.
The documentation for this product is available in HTML and PDF formats at the Cloud Manager 2.5 Documentation website.
This patch includes all of the files you need to update the Application Server 2.5.1 component of Cloud Manager to Application Server 2.5.1 Patch 1, and to update the Orchestration Server 3.5.1 component of Cloud Manager to Orchestration Server 3.5.1 Patch 1.
Cloud Manager 2.5.1 Patch 1 provides fixes for the following issues in addition to fixes provided previously as hotfixes.
Issue: A timing issue results in CPU and RAM values being overwritten before the Save Configuration job runs during provisioning. (SR 101030383971)
Fix: In this release, Cloud Manager does not attempt to set CPU and RAM values if there is an ongoing action in CMOS. This approach should honor the intended settings in the Save Configuration job and avoid the previous timing issues.
Issue: A provisioning job fails if the job times out while waiting for the customizer VM to shut down gracefully. (SR 101054777911)
Fix: If a provisioning job times out, Cloud Manager first attempts to force a shutdown of the customizer VM. The provisioning job fails only if the forced shutdown task fails.
Issue: Disks were not properly discovered from VMware because the classes for VirtualDeviceRemoteDeviceBackingInfo were not included in the discovery. When vSphereUpdater compared disks against the information in CMOS, it incorrectly identified the disks as having changes and triggered resynchronization operations for them. The number of concurrent resynchronizations can overwhelm the server, such that CMOS was busy after a vSphere boot and every 24 hours later. (SR 101099332941)
Fix: This release correctly identifies the disks that have changed and triggers resynchronization only for the ones that have actually changed.
Issue: Reports did not include information for Windows Server 2016 Clusters. (SR 101076042841)
Fix: This release adds support for Windows Server 2016 Clusters in reports.
Apply the Cloud Manager 2.5.1 Patch 1 files to your existing Cloud Manager 2.5.1 Application Server and Cloud Manager 3.5.1 Orchestration Server.
Cloud Manager 2.5.1 Patch 1 is available on the Micro Focus Patch Finder website. Specify Cloud Manager as the product, then search for patches for Cloud Manager 2.5.
Cloud Manager 2.5.1 Patch 1 provides the NCM_2.5.1_PatchUpdate1.zip file that contains the updates. The patch update consists of a ZIP file with the Cloud Manager Orchestration Server update files, and an RPM file for the Cloud Manager Application Server updates.
cmos.zip (for the Orchestration Server), which includes these files:
netiq-cloudmanager-2.5.1-12.noarch.rpm (for the Application Server)
To apply the Orchestration Server patch to your Orchestration Server, you must install the files in the cmos.zip file.
Ensure that the following prerequisites are met before you install the patch files:
Cloud Manager Orchestration Server 3.5.1 is installed, and is up and running.
Extract the files from cmos.zip and copy them to an accessible directory on the Cloud Manager Orchestration Server.
Use the following instructions to install the patch files on your Orchestration Server 3.5.1 Server and update it to version 3.5.1 Patch 1.
NOTE:A restart is required after you apply the files to your existing Orchestration Server.
NOTE:If you see an incorrect FQDN on a workload after applying the files in this patch, you might need to rediscover the VMs.
To apply the vsphere_interface.py patch file to the Orchestration Server:
Replace the old vsphere_interface.py file in the following location with the new vsphere_interface.py file from the patch:
To apply the libcustomize.pylib patch file to the Orchestration Server:
Replace the old libcustomize.pylib file in the following location with the new libcustomize.pylib file from the patch:
To apply the customizer.job patch file to the Orchestration Server:
Replace the old customizer.job file in the following location with the new customizer.job file from the patch:
To apply the customizer.jdl patch file to the Orchestration Server:
Replace the old customizer.jdl file in following location with the new customizer.jdl file from the patch:
To apply the vi-client.jar patch file to the Orchestration Server:
Copy vi-client.jar to the following location:
Restart the vSphereUpdate scheduled job.
In the Scheduler view of the Orchestration Server console, locate and select the vSphereUpdate scheduled job.
On thestop in the field.page of the Job details section of the view, locate the field, deselect its check box, and type
In the console toolbar, click, then in the Scheduler view, click . Monitor the job progress.
This step ensures that the new vi-client.jar library you applied to the Orchestration Server is transferred to the Orchestration Agent running the vSphereUpdate job. The new library fixes the vSphere updater on the agent.
To restart the Orchestration Server from the command line, enter the following command:
To apply the Application Server patch to your Application Server, you must install the files in the netiq-cloudmanager-2.5.1-12.noarch.rpm file.
Ensure that the following prerequisites are met before you install this patch:
Cloud Manager Application Server 2.5.1 is installed, and is up and running.
Extract the netiq-cloudmanager-2.5.1-12.noarch.rpm file from the patch and copy it to an accessible directory on the Cloud Manager Application Server, such as the /tmp directory.
After you have copied the patch file to the server, use the following steps to install the file:
From the location where you copied netiq-cloudmanager-2.5.1-12.noarch.rpm file, run the following command:
rpm -Uvh --nodeps netiq-cloudmanager-2.5.1-12.noarch.rpm
Run the Cloud Manager configuration program from the following location:
Choose to run an upgrade for the Cloud Manager Server.
Verify that the netiq-cloudmanager-2.5.1-12.noarch.rpm file is installed.
Log in to the Cloud Manager Web Console.
In the Web Console, click.
In the About box, verify the following:
Server version is 2.5.1 and build number is 81.1.13
Web UI version is 2.5.1 dated 12/12/2017
NetIQ Corporation strives to ensure our products provide quality solutions for your enterprise software needs. There are no known issues for this patch release.
If you need assistance with specific product issues, please contact Customer Care.
For documentation that accompanied earlier releases, visit the Cloud Manager Documentation website and scroll to Previous Releases.
We want to hear your comments and suggestions about this document and the other documentation included with this product. You can use the Documentation-Feedback@microfocus.com.link at the bottom of any page of the online documentation, or send an email to
For specific product issues, contact Micro Focus Support at https://www.microfocus.com/support-and-services/.
Additional technical information or advice is available from several sources:
Product page: https://www.microfocus.com/products/cloud-manager/
Knowledge Base articles, and videos: https://www.microfocus.com/support-and-services/
The Micro Focus Community pages: https://www.microfocus.com/communities/
For information about legal notices, trademarks, disclaimers, warranties, export and other use restrictions, U.S. Government rights, patent policy, and FIPS compliance, see https://www.microfocus.com/about/legal/.
Copyright © 2017 NetIQ Corporation. All Rights Reserved.