1 Reply Latest reply on Jan 8, 2018 2:53 PM by Sanket Mhatre

    CLM Error : callComputeAndSoftwareContainerDecommissioning.

    Sanket Mhatre

      Hi,

       

      We have installed CLM RDS 4.6.00, and integrated the CLM with AWS. On provisioning we are getting below error :

       

      Cause : Error occurred OR State transitioning not defined in the state callComputeAndSoftwareContainerDecommissioning.

      Action : Troubleshooting information is available in the CLM logs (Needs Administrator Access).

      Cause : System could not match the tags on filtered Network with either of the Tenant or the tags in the Blueprint.

      Action : Please verify that the Service Blueprint, Tenant and Network are tagged appropriately.You can see the Platform Manager logs for more details on Placement.

       

      Thanks,

      Sanket

        • 1. Re: CLM Error : callComputeAndSoftwareContainerDecommissioning.
          Sanket Mhatre

          Hi,

           

          Issue resolved,

           

          Root cause : CLM RDS 4.6.00 is pretty much out of sync with AWS offerings (since it's released pretty long back, and one need to update it to latest). For example. in RDS 4.6.00 you can see the configuration as 1 CPU , 0.62 GB RAM for t1.micro. However in reality in current date there is no such offering in AWS.

           

          To make it work, go to service designer, and in the blue-print, change the RAM from 0.62 GB to 1024 MB.

          So now, when end user orders this offering, CLM computes resources and check the offering with 1 CPU and 1 GB RAM in AWS, and automatically resolves it with t2.micro.

           

          Thanks,
          Sanket