Service offering issues

This topic was edited by a BMC Contributor and has not been approved.  More information.

As part of standard service offering instance (SOI) creation request, BMC Cloud Lifecycle Management creates and executes the following jobs in BMC Server Automation:.

  1. Virtual Guest Job
  2. Update Server Properties Job
  3. User creation job (a customized NSH Script Job) 
  4. (optional) Application software installation

If any of these jobs fail, BMC Cloud Lifecycle Management causes the SOI request to fail.

To troubleshoot issues with an SOI, determine which job is failing in BMC Server Automation and identify the root cause. For more information, see:

See also Known issues for SOIs when integrating BMC Server Automation

You canconfigure BMC Cloud Lifecycle Management to receive email notifications every time the SOI provisioning fails. A link from the email notification directs a cloud administrator to the troubleshooting section on the console from where you can view information about the stages where the SOI provisioning failed and after resolving the conflict, retry provisioning the SOI. From the console, you can also downloading log files for service offering instance failures.

Related BMC Communities video

Troubleshooting provisioning failures (3:55)

Related Knowledge Articles

You can also refer to the following Knowledge Articles from BMC Customer Support:

000090236: SOI provisioning fails with: "Please ensure cluster-switch relationship exists in the cdb"

000092466: SOI Provisioning fails with an "Error: VG creation failed: Custom Object version was not found in the BBSA response"

000085609: Logged in user can see all Service Offerings for all companies even though access has been restricted.

000089153: SOI provisioning fails with an error: "Could not retrieve any Virtual Datastore Pool"

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

Comments