4.1.00.001: Patch 1 for version 4.1.00

Note

Documentation for this patch has been moved to the Patches page. If you had bookmarked this page and happen to open it, you will be automatically redirected to the Patches page after 30 seconds.

Redirect Notice

This page will redirect to /xwiki/bin/view/Automation-DevSecOps/Client-Management/BMC-Cloud-Lifecycle-Management/clm41/Release-notes-and-notices/Patches/ in about 30 seconds.

This topic contains information about fixes and updates in this patch, and provides instructions for downloading and installing the patch.

Tip

For information about issues corrected in this service pack, see Known-and-corrected-issues.

Click here to create a PDF version of the Patch 1 release notes.

Updates

Patch 1 for BMC Cloud Lifecycle Management 4.1 provides the following updates.

Video

The following video describes the updates provided with Patch 1.

^{Use player to increase quality or switch to full screen | YouTube: What's new in BMC Cloud Lifecycle Management 4.1 Patch 1}

Ability to modify description of service offering instances

As an end user or a cloud administrator, you can now edit the description of a service offering instance from the BMC Cloud Lifecycle Management – My Cloud Services Console. An operator action - Modify Description is added to the BMC Cloud Lifecycle Management – My Cloud Services Console that enables you to change the description of an SOI.

For more information, see Modifying-the-description-of-the-service-offering-instances.

Ability to restart a service offering instance

A Restart operation is now available from the Service Instances workspace.

A cloud administrator can restart any service offering instance (supported providers are VMware, Amazon, and VMware vCloud only). An end user can restart the service offering instance from the BMC Cloud Lifecycle Management – My Cloud Services Console. When you perform the restart operation, the status of the SOI changes to Restarting. The status changes to Running after the VM is restarted successfully.

You cannot restart any platform-as-a-service (PaaS) containers from the workspace.

For more information, see Restarting-service-offering-instances.

Quick Start now supports DNS configuration during pod creation

Using Quick Start, you can now configure the DNS registration details for a VMware pod or environment network. You can configure the following DNS details for a VMware vCenter pod.

Primary DNS server
Reverse DNS server
Secondary DNS server
Primary Domain Suffix
Domain Search Order (Comma-separated List)
Reverse DNS Zone

For more information about configuring DNS registration details, see Provisioning VMs on VMware vCenter using Quick Start.

Ability to sort Load Balancer Pool names

From the Resources workspace, in the Network Containers area, if you click Manage Load Balancer, you can now sort the load balancer pools based on their names in an ascending or a descending order. The following figure shows the sort feature available for the Name field.

LB sort.png

You can also sort the VMs based on their names while adding pool entries for a selected load balancer pool. The following figure shows the sort feature for the list of compute containers.

compute container sort.png

Support for adding new networks in a pod

Whenever you create new networks in a pod in BMC Network Automation, these networks must be synced in CLM for them to be visible and to be able to provision to the new networks.

To sync pod networks in BMC Cloud Lifecycle Management:

From the BMC Cloud Lifecycle Management Administration Console, click the vertical Workspaces menu on the left side of the window and select Resources.
Under Quick Links on the left, click Pods under the General section.
Select the pod you want to synchronize.
Click the Synchronize Pod icon to synchronize the network pod with any changes to the pod since it was onboarded.
You can click the Pending Activity section opens to view the progress of the synchronization.

While creating a new network, ensure that you add all required nodes before you perform the sync pod operation. You can only synchronize new networks or new nodes which you add in BMC Network Automation. Any changes made to the pod which does not involve adding any new networks or nodes are not synchronized.

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 4.1.00.001.

Current version	Upgrade support
4.1	Patch installer installs patch 1
4.0 or earlier	Upgrade to 4.1 and then install patch 1

Preparing to install the patch

Before installing patch 1 ensure that the following conditions are met:

If you are using any of the earlier versions, upgrade to BMC Cloud Lifecycle Mangement version 4.1.
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 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
1. Generate an encrypted password:
  On the Cloud Platform Manager, go to C:\Program Files\BMC Software\BMCCloudLifeCycleManagement\Utilities.
  Run the BMCCloudLifeCycleManagementMaintenanceTool.bat/sh file.
  Click Encrypt.
  In the Password and Confirm Password fields, enter the new password.
  Click Encrypt.
  Copy the new encrypted password.
2. Update the encrypted password in the installation configuration file on the enterprise AR System:
  Go to InstallationDirectory\BMCCloudLifeCycleManagement\ and open the ARSystemInstalledConfiguration.xml file.
  Search for the BMC_AR_PASSWORD_HOSTING attribute.
  In the value field for the attribute, enter the encrypted password.
3. On the cloud AR System server, follow the same steps to update the encrypted password in the installation configuration file.
Ensure that the BMC Remedy AR System ports specified in the ARSystemInstalledConfiguration.xml file are accurate.
If the ports are not accurate, stop the enterprise AR System or cloud AR System services, updated the port numbers, and restart the service. For more information, see BMC Knowledge Article KA410544.
Take a VM snapshot and a database backup of the enterprise AR System server and Platform Manager,
Warning
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 1.

Note

For installing patch 1 on Cloud Express, place the installer file on the host and extract the files. Perform step 2 to install the patch 1.

To install patch 1:

Download and extract the patch installer and place a copy on each of the VMs that have the following components installed:
1. Enterprise BMC Remedy AR System server
2. Cloud Platform Manager
  Notes
  Install patch 1 on the enterprise BMC Remedy AR System first and then on Platform Manager.
  For Linux, extract the installer by using the tar –xvf CLMPatchInstaller4100P1.tar command.
On the Enterprise AR System server, install patch 1:
1. 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.
    Note
    You can also use the VConsole to launch the installer.
2. On the Welcome pane, note the warnings and click Next.
3. 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.
4. On the Installation Preview pane, review the summary and click Next.
Repeat step 2 on the Cloud Platform Manager.
(Optional; only if you have a high availability environment) For a BMC Cloud Lifecycle Management high availability environment:
1. On each additional or secondary enterprise AR System server, copy all files from the <CLMPatchInstaller>/files/patch/ear/P1/jars/Cloud_Portal/plugin and replace them in the<BMCCloudLifeCycleManagementInstallationDirectory>\Cloud_Portal\plugin location.

Configuring after installing the patch

You must clear cache after installing patch 1. Perform the following post configuration steps:

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.
Log on to the Mid Tier Configuration Tool.
Perform a flush cache.
The flush cache removes all items from the caches that BMC Remedy Mid Tier maintains. The next time the mid tier needs those objects, the most up-to-date versions are retrieved from the AR System server.
Clear the browser cache.
Perform the following steps to hard delete the mid-tier cache:
1. Stop the MidTier service.
2. Clear contents of the following folders:
  <BMC Software>\ARSystem\midtier\cache
  <BMC Software>\ARSystem\midtier\PluginsCache
  <Apache Software Foundation>\Tomcat6.0\work
3. Restart the MidTier service.