Open issues in version 2.1 SP1
The following table lists the issues that remain open for BMC Cloud Lifecycle Management in this service pack. A workaround, if available, is included with the issue:
Open issues in BMC Cloud Lifecycle Management version 2.1 SP1
Tracking ID | Issue |
|---|---|
QM001725577 | Attempting to create a new tag group with the same name as an existing tag group results in the name New Group for the new tag group. Repeating the attempt results in additional tag groups named New Group. |
QM001725576 | Creating a new tag group using the same name as an existing tag group can delete the existing tag group. |
QM001725460 | The tenant mapping for a network container can fail if tenants are selected from a list of available tenants spanning more than one user interface page. Only the tenant mapped from the final user interface page is mapped successfully. |
QM001724449 | If the script name for the opening port is incorrectly specified in the blueprint, the error returned during provisioning provides an unsatisfactory explanation. |
QM001723833 | The service offering ID appears in the error log even though the service offering instance blueprint is not selected for the offering. |
QM001723565 | The "Error Handling Request in CSMProvider. (ARERR 219009)" error message appears after performing an upgrade of BMC Cloud Lifecycle Management. |
QM001723404 | On a service offering instance provisioning request, if you click the Back button to view the options, the default option is automatically selected. |
QM001723363 | No validation occurs for IP address fields in the BMC Atrium CMBD service offering instance blueprint. |
QM001717578 | Attempting to simultaneously decommission multiple service offering instances that are assigned to a silver, gold, or multizone network container will fail with a critical severity error. This issue can occur with any type of service blueprint. |
None | The following tagging issues still exist:
|
Error after performing upgrade
If you receive the Error Handling Request in CSMProvider. (ARERR 219009) error message after you upgrade to SP1, perform the following steps:
- After upgrading and starting the OSGi container, wait for no less than 5 minutes and then submit a POST /csm/ProviderDefinition/search call.
- In the response for the call, find and retrieve the UUIDs for the Resource Manager Provider Definition and EC2 Generic Provider Definition.
- Stop the OSGi container.
- From BMC Remedy User, open the BMC_ProviderDefinition form in the Cloud DB.
- Search for the EC2 Generic Provider Definition entry.
- Edit the parent relationship to point to the Resource Manager ProviderDefinition entry.
- Restart the OSGi container.
- Wait no less than 5 minutes for the OSGi ecosystem to enter a stable phase.
- Submit a POST /csm/ProviderDefinition/search call again.
The EC2 Generic ProviderDefinition parent now points to the Resource Manager.