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.

Installation of Azure Provider fails

Installation of Azure Provider fails and the azure_install_log.txt contains the following entries:

LOG EVENT {Description=[Azure definition entry is not found on Cloud AR server. Please make sure that CMF:ProviderDefinition_v form is accessible. Also check csm.log file for more information.]}
LOG EVENT {Description=[No files to restore.],Detail=[File 'e:\Program Files\BMC Software\BMCCloudLifeCycleManagement\Platform_Manager\configuration\cloudservices.json' was not restored as it does not exist.]}

To workaround this issue, ensure that you install the Azure Provider manually or re-run the Azure Provider installer after cleaning up your incomplete Azure Provider installation.

Installer is unable to validate the BMC AR System Server details

While installing the Azure Provider, the installer is unable to validate the BMC AR System Server details entered and returns the following error message.

To work around this issue, ensure that you have entered the correct AR Port number. You can check the AR Port number of the BMC AR System Server installed in your environment by accessing either of the following files and searching for BMC_AR_PORT:

C:\Program Files\BMC Software\BMCCloudLifeCycleManagement\BMCCloudLifeCycleManagementInstalledConfiguration.xml
C:\Program Files\BMC Software\BusinessServiceManagementInstalledConfiguration.xml

Azure Provider is not registered or the Logical Data Centers search shows inconsistent results

After upgrade the Azure Provider is not registered or the Logical Data Centers search shows inconsistent results.

To work around this issue, check the <Platform_Manager_installation_directory>/configuration/config.ini file and ensure that the osgi.bundles for the Azure Provider exists and are set correctly.

Missing attribute details while viewing or editing the Azure Provider

After upgrading the BMC Cloud Lifecycle Management environment, when you view or edit the Azure Provider details using the Provider Registration screen, some of the attributes are missing.

To work around this issue, restart the enterprise AR System plug-in.

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.

VM placed in an incorrect availability set

In a multi-tier service offering, the VM is placed in a different availability set rather than the availability set with the correct server group name.

To work around this issue, as a cloud administrator, you must ensure that you specify correct server group name in the availability set parameter when you create a multi-tier service blueprint.

For example: In a multi-tier service blueprint, if there are two server groups (for example: VM1 and VM2), the availability set parameter name must be specified as below:

AVAILABILITY_SET_NAME#VM1 for VM1
AVAILABILITY_SET_NAME#VM2 for VM2

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:

Check that the RSCD agent version of the custom template and the Azure Provider environment are same.
Check configurations in BMC Server Automation.
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.

Inbound network path or port is not created

Inbound network path or port (endpoint) is not created automatically, when you add a new virtual machine (VM) as a Day 2 operation on an existing service.

To work around this issue, you must manually create a network path or port (endpoint) on the cloned or new virtual machine using the Day 2 operation.

While adding a server, the new server is not added to the load balancer pool

When you are adding a new virtual machine (VM) as a Day 2 operation on an existing service, the new server is not added automatically to the load balancer pool.

To work around this issue, you must add the cloned or new virtual machine manually to the load balancer pool using the Day 2 operation.