Day 2 activities are not working for proxy PaaS provider and recommendations to register the proxy PaaS provider.

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


    COMPONENT:

    Cloud Lifecycle Management


    APPLIES TO:

    Cloud Lifecycle Management 4.x



    PROBLEM:

    Day 2 activities and other operations are not working for proxy PaaS provider. CSM logs shows following entries:

    22 Dec 2016 10:12:24,226 [INFO] PUBLICPAAS - [Thread=920e1286-89e5-4bed-85fe-b39e0b196bc5::4e114ca5-70a5-4257-aca9-ec2e4034aad9(461)] [Class=SoftwareContainerStopFSM:delegateToProxy] - Proxy provider [acfc3f26-15e4-40b1-8c8b-d89ad5697220] has not implemented Stop operation on CustomContainer

    Following is an entry of this operation in providers.json file present in Platform Manager machine:


     {
                      "cloudClass":"com.bmc.cloud.model.beans.ProvidedOperation",
                      "className":"CustomContainer",-------------------------------->Short className
                      "description":"CustomContainer start",
                      "name":"CustomContainer_start",
                      "operationName":"start",
                      "configurationData":"{\"WFName\":\":<workflow name>\"}"
                   }


    CAUSE:

    Fully qualified className is not present for the operations


    SOLUTION:

    While registering proxy PaaS provider definition, make sure that the request JSON which holds the list of operations supported by the provider def has the fully qualified className mentioned.

    http://<PM machine>:<port>/csm/providerdefinition

    Following is the sample:

    {
                      "cloudClass":"com.bmc.cloud.model.beans.ProvidedOperation",
                      "className":"com.bmc.cloud.model.beans.CustomContainer", ---------->Fully qualified className
                      "description":"CustomContainer start",
                      "name":"CustomContainer_start",
                      "operationName":"start",
                      "configurationData":"{\"WFName\":\":<workflow name>\"}"
                   }


    Note: If you happen to already register with this inconsistency then it is recommended to de-register the provider definition using the API. BMC do not support/recommend any changes directly done in providers.json file without verifying it with BMC team.


    Article Number:

    000129258


    Article Type:

    Solutions to a Product Problem



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