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.

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 osgi.bundles for the Azure Provider exists and are set correctly.

Azure Provider is not found

After upgrade, you see the error <Variable>: The <Variable> provider found for <Variable> operation has a different GUID than what the system expects.

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 is set correctly.
Reimport the Azure Provider .def files.

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.

Post-deployment 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.

Software install fails for a multi-tier VM or service offering having network path in 4750 port

Software install may fail for a multi-tier VM or service offering due to unavailability of 4750 port as the network path is opened in 4750 port either during provisioning or as a post-deployment action. See Azure Provider Limitations for details.

To work around this issue, perform the following checks:

Ensure that in a multi-tier blueprint you do not have the 4750 port defined for a network path.
Ensure that while defining a post-deployment network path for a multi-tier VM, you do not specify 4750 as a port number.

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.

Unable to enable the VitalQIP IPAM for a LDC having multiple subnets

VitalQIP does not allow you to create multiple networks if subnet mask is greater than 24, so you are unable to enable the VitalQIP IPAM for a LDC having multiple subnets.

To work around this issue, see the prerequisites for VitalQIP setup for details.

Empty organization remains in VitalQIP after you have offboarded the LDC

When you offboard the LDC from BMC Cloud Lifecycle Management, the IP Addresses gets deleted from the VitalQIP but the Organization structure created for the corresponding LDC remains in the VitalQIP.

To work around this issue, you must delete the "organization" manually once the pod is deleted from BMC Network Automation. See details for configuring BNA for VitalQIP.

Error while provisioning VMs on an IPAM enabled LDC

If a VM is provisioned manually from the Azure portal on an IPAM enabled LDC, then the IP details of the provisioned VM are not updated on BNA or an external IPAM solution and the following error is displayed while provisioning any other Azure VM:

Error: Error occurred while creating one or more resource sets.
       Error Resolution: Please contact System Administrator.
       Error ID: BMC-CLMT-10500029
       Transaction ID: adda6d69-4efe-4f83-8662-b4ed68fc6ecb
       Root Cause Info:
       Severity: CRITICAL
       Error: PollingTimerThread exception Networking.DeploymentVNetAddressAllocationFailure-Unable to allocate the required address spaces for the deployment in a new or predefined subnet that is contained within the specified virtual network.

To work around this issue, you must manually register the IPs of the existing Azure VMs provisioned in the Azure Virtual Network, prior to enabling IPAM for the LDC (Azure Virtual Network) in BMC Cloud Lifecycle Management solution.

Fails to acquire IP for a second instance in case of multi-tier SOI provisioning using an IPAM enabled LDC

If multiple instances are requested in a SOI for an IPAM enabled LDC, the SOI completes successfully but the submission task fails with the following error in csm logs:

cloudClass" : "com.bmc.cloud.model.beans.TaskError",
    "errorAction" : "Troubleshooting information is available in the CLM logs (Needs Administrator Access).",
    "errorCause" : "Following error was encountered during operation acquireAddresses : Response Description:Duplicate object '11.0.1.4' of type 'host' already exists in the database.",
    "errorID" : "BMC-CLMT-10800259",
    "errorTrace" : "com.bmc.cloud.provider.bbnaprovider.internal.IPAMServiceException: Response Description:Duplicate object '11.0.1.4' of type 'host' already exists in the database.\r\n\tat com.bmc.cloud.provider.bbnaprovider.helper.IPAMServiceIntegrationHelper.acquireAddresses(IPAMServiceIntegrationHelper.java:198)\r\n\tat com.bmc.cloud.provider.bbnaprovider.fsm.LogicalDataCenterAddressPoolAcquireAddressesFSM.start(LogicalDataCenterAddressPoolAcquireAddressesFSM.java:61)\r\n\tat sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\r\n\tat sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)\r\n\tat

To work around this issue, ensure that you have configured BNA to support the third party IPAM solution. While configuring BNA, in the Global Properties field, you must set ipamSerializeThirdPartyRequests=true to enable BMC Network Automation to serialize concurrent requests for an acquire IP address operation. See Configuring BMC Network Automation to support the use of a third-party IPAM solution for details.

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.

Linux VM templates do not establish an SSH connection

Some Linux VM templates do not allow you to establish an SSH connection in Windows Azure, so a Linux VM provisioning fails when you use these specific templates. For example: CentOS-RightImage does not allow an SSH connection.

Provisioned VM displays incorrect disk size

A provisioned Windows Azure VM displays an incorrect disk size in the Servers link bar of the My Services tab.