Patch 2 for Service Pack 1: 3.1.01.002
This topic contains information about fixes and updates in this patch, and provides instructions for downloading and installing the patch.
For information about issues corrected in this patch, see Known and corrected issues.
Patch 2 for BMC Cloud Lifecycle Management 3.1 Service Pack 1 provides the following updates.
Refresh IP address
In earlier releases of BMC Cloud Lifecycle Management, if the IP address of a virtual machine changed, the IP address in BMC Cloud Lifecycle Management remained unchanged. Now, if the IP address of a VM changes due to any reason such as the IP renewal or DHCP lease expires, the Refresh API detects the change and updates the cloud database with the appropriate IP address.
By default, if the compute container is attached to a load balancer or a firewall, the IP address is not refreshed. You can use the
override IP flag to refresh the IP address even if the compute container is attached to a load balancer or a firewall. For more information, see ComputeContainer refreshIP request.
Ability to specify a port range while creating firewall rules
You can now specify a port range while creating distributed or perimeter firewall rules. This enables you to create one firewall rule instead of creating multiple rules for multiple ports.
You must upgrade to BMC Network Automation 8.5 to be able to specify the port range. For more information about BMC Component products version, see Component BMC product service pack and patch levels.
For example, in earlier versions of BMC Cloud Lifecycle Management, if you wanted to block port numbers from 8000 to 8010, then you were required to create 10 firewall rules. In this release, while creating a firewall rule, you can specify a port range from 8000-1010 and all ports in the range are blocked.
A Port Range option button allows you to specify a single port number or a range of port numbers using a dash. For example, 7717-9080.
The following figure describes the newly added option button.
For information about creating firewall rules with a port range, see Creating and editing firewall rules.
Ability to specify a disk with a 0GB size
When adding additional disks to a service through a post-deployment action, you can now specify a disk size of 0GB for IBM LPARs. This enables you to create two adapter pairs (WWPN) for multipathing.
You can specify 0GB size only for IBM LPAR service offerings. Do not specify 0GB for any other service offerings.
Simplified disk names
Virtual machine disks will now have display names of Disk1, Disk2,.. Diskn according to the order in which those disks were provisioned. This provides a simpler and clearer view of the disks in the BMC Cloud Lifecycle Management user interface. The original name of a disk is available in the Description field in the CloudDB. You can sort the system disks by the Name field on the Server details screen.
If you want existing disks to benefit from the change in naming, run the DiskRenameUtility.zip after you install the patch. For more information about running the utility, see Configuring after installing the patch.
The simplified disk names feature is only applicable for the virtual system disks or local disks. This feature is not supported for Amazon Web Services platform.
Utility to perform cleanup of the reconciliation job runs and events history
In previous releases of BMC Cloud Lifecycle Management, there is no mechanism to clean up the reconciliation job runs and reconciliation job events history records. As the number of records grow, a number of issues occur related to reconciliation jobs used by BMC Cloud Lifecycle Management. To clean up the reconciliation job run and job events history, a .def file is available, with escalation objects.
After you import the file in your environment, you can configure the number of days a record should be maintained in BMC Cloud Lifecycle Management. You can download the utility from the following location:
For more information, see Performing clean up of reconciliation job runs and events history.
Downloading the patch
For download instructions, see Downloading the installation files.
Supported upgrade paths
The following table describes the supported upgrade paths if you want to install BMC Cloud Lifecycle Management version 3.1.01.002. If your current version is 3.1, you need to upgrade to 3.1 SP1 to install Patch 2.
|Current version||Upgrade support|
|3.1 or earlier||Upgrade to 3.1 Service Pack 1 (3.1.01)|
Patch installer installs 3.1.01 Patch 1 and Patch 2 together
You can consult thetable to view the issues that are resolved in Patch 1 and 2.
|3.1.01.001||Patch installer installs 3.1.01 Patch 2|
Preparing to install the patch
The following table describes the steps you need to perform before installing this patch.
|1.||Upgrade to BMC Cloud Lifecycle Management 3.1.01 before upgrading to patch 2. |
For more information about upgrading, see Upgrading.
|2.||Ensure that the supported products are at the latest service pack or patch level. |
For more information about the supported product versions, see Component BMC product service pack and patch levels.
If you are installing patch 2 on BMC Cloud Lifecycle Management 3.1.01, then perform the steps 3.1-3.4 before installing this patch.
Skip the steps if you have already installed Patch 1.
(Optional) Install only if you require the fix for QM001790410, else, skip to step 3.2.
QM001790410: Issues with SOI provisioning rollback behavior cause problems such as improper clean up of VMs from the infrastructure or IP address conflicts.
Upgrade BMC Server Automation to version 8.3 Service Pack 2 and then apply the hotfix. Contact BMC Customer Support to obtain the hotfix.
Perform the following steps to install the hotfix on BMC Server Automation version 8.3 Service Pack 2
(Perform this step only if you have skipped step 3.1)
Install the hotfix for BMC Server Automation 8.3 from the following location.
Perform the following steps to install the hot fix on BMC Server Automation version 8.3
If you have changed the administrator user password for the enterprise AR System and cloud AR System after the last time you installed BMC Cloud Lifecycle Management, you must ensure that the passwords match the installation configuration file.
If the passwords do not match, the installation fails.
Perform the following steps to ensure that the passwords match
Take a VM snapshot and a database backup of the enterprise AR System server, cloud AR System, Platform Manager, and BMC Atrium Orchestrator.
Installing the patch can affect the AR objects in a non-overlay mode. Ensure that you follow the best practices for customizations.
Ensure that JAVA_HOME variable is set on the servers where you are installing the patch. On Linux servers, ensure that X11 libraries are installed.
Installing the patch
This topic describes the procedure to install patch 2.
For installing patch 2 on Cloud Express, place the installer file on the host and extract the files. Perform step 2 to install the patch 2.
To install patch 2:
- Download and extract the installer and place a copy on each of the VMs that have the following components installed:
- Enterprise BMC Remedy AR System server
- Cloud BMC Remedy AR System server
Cloud Platform Manager
BMC Atrium Orchestrator Platform
Install patch 2 on the components in an incremental manner. Install patch 2 on the enterprise BMC Remedy AR System first, then on cloud AR System server, then Platform Manager, and finally on BMC Atrium Orchestrator Platform server.
For Linux, extract the installer by using the tar –xvf CLMPatchInstaller3101P2.tar.gz command.
- On the Enterprise AR System server, install patch 2:
Start one of the following installation programs:
- On Microsoft Windows, double-click the setup.cmd file.
On Linux, navigate to the \CLMPatchInstaller\Disk1 location and run the setup.bin file by using Xmanager.
With Xmanager, X applications installed on remote UNIX-based computers run seamlessly with Windows applications side by side.
You can also use VConsole to launch the installer.
- On the Welcome pane, note the warnings and click Next.
- On the Directory selection pane, navigate to the location on the host where you want to install the BMC Cloud Lifecycle Management patch installer files and click Next.
You can accept the default value if you do not have a specific location for the installation files.
- On the Installation Preview pane, review the summary and click Next.
- Start one of the following installation programs:
- Repeat step 2 on the Cloud AR System server.
- Repeat step 2 on the Cloud Platform Manager.
- Repeat step 2 on the server where BMC Atrium Orchestrator Platform is installed.
- (Optional; only if you have a high availability environment) For a BMC Cloud Lifecycle Management high availability environment, perform the following steps:
- On each additional or secondary enterprise AR System server, copy all files from the <CLMPatchInstaller>\files\ear\P2\jars\Cloud_Portal\plugin and replace them in the <BMCCloudLifeCycleManagementInstallationDirectory>\Cloud_Portal\plugin location.
- On each secondary BMC Atrium Orchestrator Configuration Distribution Peer, copy all files from the <CLMPatchInstaller>\files\ao\P2\nsh location and replace them in the <NSH Installation Directory>\scripts location.
- If you have installed the NetApp Storage adapter version 20.12.02, copy the jar files from the <CLMPatchInstaller>\files\ao\P2\adp\jars location and replace them in the <AO-CDP InstallationDirectory>\server\grids\<GRID NAME>\library\adapters\implementations\bmc-adapter-netapp-storage-actor_20.12.02.00_1 directory.
Configuring after installing the patch
The following table describes the steps you need to perform after installing this patch.
Run the DiskRenameUtility utility to apply the simplified disk names update for the existing disk names.
Before running the utility, ensure that:
Perform the following steps to run the utility
Available modes for the utility.properties file
To run the DiskRenameUtility, you must configure the utility.properties file to run in a suitable mode. You can configure the following modes in the utility.properties file:
|2.||Clear the mid-tier cache.|
If the mid-tier used by the BMC Cloud Lifecycle Management console is different than the mid-tier running on the enterprise AR System server, then you need to clear the cache.
|3.||Clear the browser cache.|
Delete the mid-tier cache.
Perform the following steps to hard delete the mid-tier cache