Unable to onboard existing VM via Cloud API "ServiceOfferingInstance onboard" request

Version 2
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    Cloud Lifecycle Management


    APPLIES TO:

    BMC Cloud Lifecycle Management



    PROBLEM:

     

    Environmental Details: BMC Cloud Lifecycle Management 2.x, 3.x

      

    Unable to onboard existing VM via Cloud API "ServiceOfferingInstance onboard" request

    [in csm.log]

    04 Apr 2013 15:08:57,745 [ERROR] API - [Thread=8db4ad4e-3d15-4f47-ba88-811b43049b4b::0f63627b-69a1-48ea-ad5d-cbf4c5dc7417(107)] [Class=BaseBBSATaskExecHelper:getBBSAVGName] - Could not find VirtualGuest in BBSA
    04 Apr 2013 15:08:57,745 [ERROR] API - [Thread=8db4ad4e-3d15-4f47-ba88-811b43049b4b::0f63627b-69a1-48ea-ad5d-cbf4c5dc7417(107)] [Class=VirtualGuestOnboardExecHelper:execute] - VG onboard failed: Could not find VirtualGuest in BBSA


    [in json response]

    "errorCause" : "VirtualGuest onboard failed: Could not find VirtualGuest in BBSA",
    "errorID" : "BMC-CLMT-10100023",
    "errorTrace" : "java.lang.IllegalArgumentException: Could not find VirtualGuest in BBSA\r\n\tat com.bmc.cloud.provider.bbsaprovider.task.BaseBBSATaskExecHelper.getBBSAVGName(BaseBBSATaskExecHelper.java:1480)\r\n\tat com.bmc.cloud.provider.bbsaprovider.task.BaseVirtualGuestTaskExecHelper.getBBSAVGName(BaseVirtualGuestTaskExecHelper.java:41)\r\n\tat com.bmc.cloud.provider.bbsaprovider.task.VirtualGuestOnboardExecHelper.onboard(VirtualGuestOnboardExecHelper.java:96)\r\n\tat com.bmc.cloud.provider.bbsaprovider.task.VirtualGuestOnboardExecHelper.execute(VirtualGuestOnboardExecHelper.java:52)\r\n\tat com.bmc.cloud.task.scxml.actions.ExecAction.doExecute(ExecAction.java:93)\r\n\tat com.bmc.cloud.task.scxml.actions.CSMBaseAction.execute(CSMBaseAction.java:101)\r\n\tat org.apache.commons.scxml.semantics.SCXMLSemanticsImpl.executeActions(SCXMLSemanticsImpl.java:239)\r\n\tat org.apache.commons.scxml.SCXMLExecutor.reset(SCXMLExecutor.java:252)\r\n\tat org.apache.commons.scxml.SCXMLExecutor.go(SCXMLExecutor.java:351)\r\n\tat com.bmc.cloud.task.impl.TaskImpl.executeTask(TaskImpl.java:440)\r\n\tat com.bmc.cloud.task.impl.TaskImpl.fireEvent(TaskImpl.java:650)\r\n\tat com.bmc.cloud.taskmanager.impl.EventManager$EventWorker.run(EventManager.java:307)\r\n\tat java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)\r\n\tat java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)\r\n\tat java.lang.Thread.run(Thread.java:662)\r\n",

     


    SOLUTION:

     

    Legacy ID:KA393889

      

    To troubleshoot this issue check the external ID of the VM. Use the following BSA web service call to debug further.

    https://<bsahostname>:10843/type/PropertySetClasses/SystemObject/Server/?name=test-33&username=BLAdmin&password=<password>&role=BLAdmins

    Substitute the <bsahostname> and BLAdmin <password> for their actual values (change the port too if the web service port is different). Compare the URI  from this call against what is there in the request json.

      
    Related Products:  
       
    1. BMC Cloud Lifecycle Management

     


    Article Number:

    000055684


    Article Type:

    Solutions to a Product Problem



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles