OpenStack Provider issues

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

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

You can check the following log files for entries that might help diagnose the problem:

Log file	Location
csm.log	Windows: C:\Program Files\BMC Software\BMCCloudLifeCycleManagement\Platform_Manager\logs\csm.log Linux: /opt/bmc/BMCCloudLifeCycleManagement/Platform_Manager/logs/csm.log
processes.log	Windows: C:\Program Files\BMC Software\AO-Platform\CDP\tomcat\logs\processes.log Linux: /opt/bmc/AO-Platform/CDP/tomcat/logs/processes.log

Note

You can also check the OPENSTACK_PROXY_LOG_FILE attribute defined in the OpenStack.properties file. If a value is specified for this attribute, the REST request/response detailing the issue is printed in this file.

LDC search does not return any results

LDC search does not return any results even though all the projects configured in OpenStack are not already onboarded.

To work around this issue, check logs for error details and update configuration.

The potential reasons can be:

Invalid user credentials provided while registering accounts.
Issues in accessing OpenStack environment.

Timeout in BMC Cloud Lifecycle Management results erroneous OpenStack operation

Timeout in BMC Cloud Lifecycle Management before completing operation in OpenStack results in error.

A potential reason could be a delay in the completion of the operation in OpenStack. To work around this issue, you must edit the provider and increase the Task Poll Count and Poll Interval and then restart the Platform Manager.

The Operating System value populated for provisioned server is coming up as UNKNOWN

If the Operating System value populated for provisioned server is coming up as UNKNOWN, then the Administrator needs to add the Operating System name to the metadata tag of image.

For example: Use the following command to add the Operating System name as metadata, where the Glance component is installed.

glance image-update <image id> --property os-name=<operating system name>

Note

To use remote connect for the Windows server from BMC Cloud Lifecycle Management, the metadata for property os-name should start with Windows.

For example: Windows Server 2008 R2; Windows 2008 R2.

Failure in OpenStack operations due to poll timeout

If there are frequent failures in OpenStack operations due to poll timeout, then the Administrator can increase the poll interval or poll count or both.