$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')
 
 

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.

BMC Cloud Lifecycle Management 3.1 ... Troubleshooting Third party platform integration issues

OpenStack provider issues

This topic contains information to help you troubleshoot the OpenStack resource 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

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


The following table contains explanations and workarounds for problems you might encounter when working with the OpenStack resource provider:

Problem

Solution

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

Check logs for error details and update configuration. Potential reasons could be: 
1. Invalid user credentials provided while registering accounts.
2. Issues in accessing OpenStack environment.

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

Potential reasons could be delay in completion of the operation in OpenStack. You need to edit the provider and increase 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.

Admin needs to add the Operating System name to the metadata tag of image.
For example: You can 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 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.

Incase of frequent occurrences, Admin has to increase the poll interval and/or poll count.

Was this page helpful? Yes No Submitting... Thank you
Last modified by Jolly Sharma on Mar 24, 2013
openstack troubleshooting

Comments

Third party platform integration issues
Savvis provider issues
© Copyright 2020 BMC Software, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2020 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.