Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Azure Provider issues

See the following sections for information about troubleshooting issues of the Azure Provider:

Note

You can check the csm.log file at the following locations for entries that might help diagnose the problem:

  • (Windows)  C:\Program Files\BMC Software\BMCCloudLifeCycleManagement\Platform_Manager\logs\csm.log
  • (Linux) /opt/bmc/BMCCloudLifeCycleManagement/Platform_Manager/logs/csm.log

For information about troubleshooting BMC Cloud Lifecycle Management, see Troubleshooting.

Unable to create an Azure Provider account

Unable to create an Azure Provider account because an invalid REST API version is entered while registering an Azure Provider.

To work around this issue, validate the Subscription ID and Management Certificate details entered while creating an Azure account.

User provisioning fails

If user provisioning fails, verify that all conditions of the Azure Password Policy have been met.

Software install fails

Post-deployment software install may fail due to changes in the IP Address of the provisioned VM, when it is restarted. See Azure Provider Limitations for details.

To work around this issue, perform the following steps:

  1. Check that the RSCD agent version of the custom template and the Azure Provider environment are same.
  2. Check configurations in BMC Server Automation.
  3. Run job from BMC Server Automation and test for successful execution.

Hosted service name is invalid

The hosted service name is invalid or contains an illegal character in path at index 102 (https://management.core.windows.net/).

To work around this issue, change the Service Offering Instance (SOI) name.

DNS name is already taken

If the specified DNS name is already taken, ensure that the Cloud Service name is unique across Azure DNS and is not consumed by any other service. You must change the SOI name to resolve the issue.

Timeout error occurs during polling for customization of the VM

If the timeout error occurs during polling for customization of the VM in Azure, you must increase the poll parameters for the Azure Provider.

Resource exhausted in Azure subscription

If resource is exhausted in your Azure subscription, then you must increase the subscription level, because each subscription has a fixed capacity for all artifacts like Cloud Service, Storage Accounts, Affinity Groups, and CPU Cores. For details about your subscription entitlement, refer to the Microsoft Azure Subscription Policy.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*