This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.
Cloud Lifecycle Management
BMC Cloud Lifecycle Management
Trying to provision a new SOI results in the VG job getting executed in BSA, but failing after a short time with:
BMC Cloud Lifecycle Management 3.1.x
This problem can occur if CLM is configured such that the VM is using a static IP address and CLM is registering the VM by IP address in BSA.
BSA tries to create a VM with the name of the IP address in VMware and if there is already a system existing with the same name, this error is thrown.
Because this causes a failure in CLM, the provisioned system is rolled back and the IP address released back to BNA to be used for the next provisioning request. This is why all subsequent provisioning jobs are affected.
To Resolve this error
1. Exclude the IP address in BNA so it is not handed out to the next provisioning request.
2. If the system that already exists in VMware is no longer required, remove it.
3. Configure CLM to register the server by hostname since the generated hostname will be different on each request.
- BMC Cloud Lifecycle Management