Corrected issues in version 2.1 SP2

Various

This service pack also contains the installation fixes listed in Corrected-issues-for-Patch-1-for-Service-Pack-1-for-version-2-1-00.

QM001746376

The Approval Required change type created a change request whose requested start date was before the earliest start date, which resulted in an expedited request.

QM001745554

Refreshing a service offering instance failed if a VM name mismatch cbetween the BMC BladeLogic Server Automation enrolled name and the VMware vCenter name.

QM001745502

Onboard failed if a VM name mismatch occurred between the BMC BladeLogic Server Automation enrolled name and the vCenter name.

QM001739806

You could not offboard a service offering instance. This fix was previously included in SP1 Hotfix 5.

QM001739195

User ID and Transaction ID were not passed to BMC Atrium Orchestrator callouts. This fix was previously included in SP1 Hotfix 5.

QM001737688

A cloud administrator could not refresh the attributes of VMs in a service offering instance. This fix was previously included in SP1 Hotfix 5.

QM001737607

Add/Remove Data/Customer NIC functionality was not working in the API. This fix was previously included in SP1 Hotfix 5.

QM001735313

When the display resolution was set to 1280x800 on the BMC Cloud Lifecycle Management Cloud Administration console, some of the buttons were not visible. This fix was previously included in SP1 Hotfix 3.

QM001733450

JDK requirements for target servers were not documented.

QM001733225

Step 16 in Installing BMC Cloud Lifecycle Management on Linux contained a typographical error.

QM001732504

X11 and other dependent package requirements were not documented for Linux servers.

QM001732502

The following details were not documented for Oracle databases in the Database-requirements topic: Number of Redo Log Files, Redo log file size, Data Table Space size, and Temp Table Space size.

QM001732499

Database Unicode and character set requirements were not documented.

QM001732498

Oracle Client software needed to be installed on CLM-ITSM, CLM-CLOUDAR, CLM-BBSA, CLM-ATRIUMWS, and CLM-BBNA.

QM001732497

The /tmp partition requirements were not documented.

QM001732496

The disk space requirements for installing component products on target servers were not clearly documented.

QM001732495

The documentation was unclear about Linux based deployments requiring you to run the installer on a Microsoft Windows server to complete the BMC ProactiveNet Performance Management installation.

QM001731993

The user interface contained a typographical error on the Edit Compute Pool window.

QM001730718

In the Overview section of the BMC Cloud Lifecycle Management My Cloud Services console, the count of load balancers and firewalls sometimes appeared as 0 rather than the actual number. This fix was previously included in SP1 Hotfix 2.

QM001729946

Onboarding existing VMs using the BMC Cloud Lifecycle Management API would fail. This fix was previously included in SP1 Hotfix 2.

QM001724168

Cloud end users could not provision a bare-metal VM from the BMC My Cloud Serivces console. This fix was previously included in SP1 Hotfix 1.

QM001723404

When creating a service offering instance request for provisioning, clicking the Back button did not display the selected options.

QM001723142

Generated service request IDs for service provisioning did not have the required REQ prefix.

QM001722377

The user interface displayed an incorrect warning message when you deleted a server from a load balancer pool.

QM001720678

BMC Cloud Lifecycle Management would not connect to BMC BladeLogic Server Automation if the BLAdmin password contained the # symbol.

QM001719224

The product needed to add a field for External Port to the Manage Virtual Loadbalancer window.

QM001719136

Performing a quick sync on the cluster did not update the available hosts in vCenter.

QM001715800

The Compute Container pane showed the Size of Disk number in megabytes instead of gigabytes. This fix was previously included in SP1 Hotfix 2.

QM001715726

A stop action was called once for every server in a service offering instance. This fix was previously included in SP1 Hotfix 2.

QM001715387

When a BMC BladeLogic Network Automation job failed during container decommissioning, the error was omitted from the recent activity log.