OpenStack Provider issues

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

Note

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.

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

After upgrading the OpenStack Provider, the OpenStack 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 OpenStack Provider exists and is set correctly.

OpenStack 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 osgi.bundles for the OpenStack Provider exists and is set correctly.
  • Reimport the OpenStack Provider .def files.

Missing attribute details while viewing or editing the OpenStack Provider

After upgrading the BMC Cloud Lifecycle Management environment, when you view or edit the OpenStack 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.

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: 

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

Timeout in BMC Cloud Lifecycle Management results in 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.

Error while modifying the CPU count and memory size for a server

While modifying the CPU count and memory size for a server, you get the following error:

To work around this issue, you must create a custom flavor in OpenStack that matches the current flavor of the server on which the Day 2 operation is performed. The two flavors should match in all parameters except the parameter that is to be modified (CPU or RAM).

For example:

If the server is provisioned using the m1.tiny flavor with the following specifications:

  • CPU : 1
  • RAM : 512
  • Root : 1
  • Ephemeral : 1

And you try to modify its RAM to 1024, there has to be a custom flavor existing in OpenStack with the following parameters that you use for modifying the RAM:

  • CPU : 1
  • RAM : 1024
  • Root : 1
  • Ephemeral : 1

Server is not decommissioned

The OpenStack server is not decommissioned from BMC Server Automation when SOI provisioning fails due to failure in software installation.

Related topic

Known and corrected issues

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

Comments