Corrected issues in version 2.1.00
This topic describes the corrected issues in this release. The issues are organized by components and BMC products:
BMC Cloud Lifecycle Management corrected issues
BMC Analytics for Business Service Management
BMC Atrium Core corrected issues
BMC Atrium Orchestrator Platform
BMC BladeLogic Network Automation
BMC BladeLogic Server Automation
BMC Capacity Management - Capacity Optimization
BMC Dashboards for Business Service Management
BMC Performance Manager for Virtual Servers
BMC ProactiveNet
BMC Remedy Action Request System (BMC Remedy AR System)
BMC Remedy IT Service Management Suite (BMC Remedy ITSM)
BMC Service Request Management
BMC Cloud Lifecycle Management corrected issues
The following table lists the corrected issues in this release of BMC Cloud Lifecycle Management:
Issue | Description |
|---|---|
QM001713822 | Dialog boxes launched from the BMC Cloud Lifecycle Management Administration Console or the BMC My Cloud Services Console now fit properly in the browser window in Internet Explorer 8.0.7600.16385. |
QM001705662 | On Linux operating systems, the installation of the Platform Manager now finishes without a warning message. |
QM001704653 | On Linux operating systems the BMC Atrium Orchestrator Application Adapter for BMC BladeLogic Server Automation now starts during post-installation configuration. |
QM001704050 | The installer now verifies the existence of the user if you use an existing installation of BMC Remedy AR System, BMC Atrium Core, and BMC Remedy ITSM with BMC Cloud Lifecycle Management 2.0 when the installer-created BMC Atrium Orchestrator user already exists. |
QM001702877 | When you attempt to decommission a service offering instance (SOI) that was powered on in XENCenter on a XENServer, the decommission no longer fails. |
QM001701106 | If service provisioning fails when the Distributed Resource Scheduler (DRS) is not enabled on a VMware virtual cluster, an informative error message is now displayed. |
QM001700959 | The BMC Cloud Lifecycle Management Installer now displays the Modify Existing Deployment option to continue the previous installation session. |
QM001698608 | You can no longer add blank user-defined requirements in a service blueprint. |
QM001698602 | When adding user defined requirements to a component in a service blueprint, clicking Add Requirement now creates a new entry instead of trying to edit the first one. |
QM001698316 | The BMC Cloud Lifecycle Management Installer now displays the Modify Existing Deployment option to continue the previous installation session whenever a post-installation task fails for a component and you restart the installer. |
QM001689824 | The BMC Cloud Lifecycle Management Installer now manages parentheses programmatically in folder path names. |
QM001689276 | BMC BladeLogic Adapter version 7.6.02.02 did not work if the computer had no internet connection. |
QM001689232 | The BMC Cloud Extension Pack installation failed on a secondary server in a server group environment. |
QM001689214 | The VM provisioning request stayed in the Implementation in progress state upon BMC Atrium Orchestrator failure. |
QM001688200 | BMC BladeLogic Server Automation sometimes failed to deprovision a VM upon request to decommission multiple VMs. |
QM001688193 | You can no longer specify multiple host names for a single product installation when only one is valid. |
QM001687694 | The BMC Service Request Management Console showed the Completed successfully status even though the network container creation task failed. |