Patch 1 for Service Pack 2 for version 2.1.00

This section contains information about BMC Cloud Lifecycle Management 2.1 SP2 Patch 1 (2.1.02.01).

Note

For information about the product updates included in SP2, see Service Pack 2 for version 2.1.00.

Before you begin

This patch requires BMC Cloud Lifecycle Management 2.1 SP2.

Obtaining the patch files

To download the patch files for BMC Cloud Lifecycle Management 2.1 SP2 Patch 1, see Obtaining, downloading, and verifying the installation files.

Installing the patch

Follow the procedures in this section to apply the patch for

  • Cloud Platform Manager
  • Enterprise BMC Remedy AR System server
  • Cloud BMC Remedy AR System server

To apply the patch to Cloud Platform Manager

  1. Stop the Platform Manager service (BMC_CSM for Microsoft Windows and BMCCSM for Linux).
  2. Make a backup of the <$Platform_Manager>\lib folder.
  3. Replace all the binary files in the <$Platform_Manager>\lib folder with the binary files in the patch zip file: Platform Manager/lib folder.
    Do not remove any binary files that were added as a part of a customization. The lib folder contains 66 binary files.
  4. Make a backup of the cmdb-api-7.6.04-SNAPSHOT.jar file in the .../BMCCloudLifeCycleManagement/Platform_Manager/3rdParty/ folder.
  5. Move the com.bmc.cmdb.api7604.jar file in the patch zip file to the .../BMCCloudLifeCycleManagement/Platform_Manager/3rdParty/ folder.
  6. Rename the com.bmc.cmdb.api7604.jar file to cmdb-api-7.6.04-SNAPSHOT.jar.
  7. Make sure the permissions are set correctly (chmod +755).
  8. Clear the cache folder: <installation directory>/BMCCloudLifeCycleManagement/Platform_Manager/configuration/org.eclipse.osgi
  9. Start the Platform Manager service (BMC_CSM for Microsoft Windows and BMCCSM for Linux).

To apply the patch to the enterprise BMC Remedy AR System server

  1. Make a snapshot of the enterprise BMC Remedy AR System server before applying the patch.
  2. Connect to the enterprise BMC Remedy AR System server by using BMC Remedy AR System Developer Studio.
  3. From the enterprise BMC Remedy AR System server, import all the files in the Enterprise AR folder from the zip file.
  4. While importing the objects, select the Replace Objects on the Destination Server option and verify that the other options are not selected.
  5. Copy the cloud-plugin.jar file to the <installation directory>BMCCloudLifeCycleManagement/Cloud_Portal/plugin folder.
  6. Restart the enterprise BMC Remedy AR System server.

To apply the patch to the cloud BMC Remedy AR System server

  1. Make a snapshot of the cloud BMC Remedy AR System server before applying the patch.
  2. Connect to the cloud BMC Remedy AR System server using BMC Remedy AR System Developer Studio.
  3. From the cloud BMC Remedy AR System server, import all the files in the Cloud AR folder from the zip file.
  4. While importing the objects, select the Replace Objects on the Destination Server option and verify that the other options are not selected.

Corrected issues

The following BMC Cloud Lifecycle Management issues are corrected by this patch:

Issue

Description

QM001740787

Could not tag a tenant.

QM001741318

Tagging an onboarded tenant created an extra TENANT tag.

QM001748153

There was a GUID mismatch in in the all_providers.json and provider_definition.json files.

QM001750648

Nested resource pools caused the VMware vCenter sync to fail.

QM001745707

The status for storage service requests did not change from In progress.

QM001748774

When a cloud end user selected Operator Actions > Extend for a service offering instance (SOI), the post deploy actions were no longer displayed for that SOI.

QM001748777

If the value of PortgroupName was a string rather than a VLAN number, the Onboard VM API call failed.

QM001748815

If the value of PortgroupName was a string rather than a VLAN number, the AddNetworkInterface API call failed.

QM001757293

The policy engine could not match the tags on filtered network containers with either the tenant or the tags in the service blueprint.

QM001751696

For an onboarded VM, the load balancer entries and firewall rules could not be created from the BMC Cloud Lifecycle Management UI.

QM001753639

After deploying new JAR files, the following class loader timing error appeared in some cases:
java.lang.NoClassDefFoundError

QM001753636

The SOI onboard function did not handle the scenario where a virutal machine (VM) was associated to port groups that have similar name patterns. For example, port groups VLAN-411 and VLAN-4117.

QM001755299

A failure in the SOI extend operation resulted in SOI decommission.

QM001756723

When a post deploy action was attempted on an Amazon EC2 instance, no error message was propagated to the UI. The modify request status remained at 50% complete.

QM001756321

The rollback process for the SOI onboard action did not clean up all of the cloud database resources.

QM001756325

The VM could be onboarded even if there was a mismatch in the Tenant and Container input parameters.

QM001755335

Could not deploy a VM with the domain specified in the Virtual Guest Package.

QM001744033

If both the Amazon EC2 provider and Savvis providers were used in the same BMC Cloud Lifecycle Management environment, all requests to the Savvis WebService failed to authenticate, failed to create a network container, and failed to provision the requested VM.

QM001756750

Missing properties and relations in the onboarded SOI made it unequal to the provisioned SOI.

QM001747904

Could not map more than 17 compute pools to a network container.

QM001756790

Could not remove the BMC BladeLogic Network Automation provider from the BMC Cloud Lifecycle Management Console.

QM001743854

A detach storage issue occurred when multiple storage devices were attached to a single VM.

QM001758819

The SOI was not decommissioned by the auto decommission feature and remained in the terminated state.

QM001754748

In the BMC Cloud Lifecycle Management – My Cloud Services Console, the host name displayed was taken from the serverHostname field in the ComputeContainer_v form and not from the Name field.

QM001761229

Setting BBSA_REGISTER_SERVERS_BY_HOSTNAME to true in the providers.json file allowed template provisioning to be registered by host name, but physical server provisioning was still registered by IP address.

QM001761668

The VMware vCenter sync and refresh did not update the attributes of objects (for example, VDR, VH, VRP) in the cloud database.

QM001761436

Provisioning failed with the following message: ERROR (120039): The operation violates the cardinality constraint of the relationship.

QM001762144

The tokenID was not in the correct format for VDS, VRP, and VC. If the VMware vCenter server was not accessible from the platform manager server by name, the token ID would not be updated for the VMware vCenter. (The token ID uses the VMware vCenter name in forming the ID.) If the VMware vCenter was not accessible by name, the token ID was the same as the external ID.

QM001762146

Multiple, generic provider instances were not supported.

Updated BMC product support for this patch

This patch, BMC Cloud Lifecycle Management version 2.1 SP2 Patch 1, has been tested with and is compatible with BMC Server Automation 8.2.04.

Was this page helpful? Yes No Submitting... Thank you

Comments