Terremark Provider issues
See the following sections for information about troubleshooting issues of the Terremark Provider:
You can check the following log files for entries that might help diagnose the problem:
Log file | Location |
|---|---|
csm.log | Windows: |
Cannot access provisioned VM with the credentials
Cannot access provisioned VM with the credentials provided while requesting a service.
To work around this issue:
- On Windows, access the VM using "Administrator" as the user ID and use the password you provided while provisioning.
- On Linux VMs, use the SSH key configured while registering the provider. In case of password policy changes, contact Terremark support.
Operation was unsuccessful
If the operation was unsuccessful due to Terremark API server unavailability, contact Terremark support.
VM provisioning fails
If the VM provisioning fails due to incorrect mapping of LDC, you must ensure that the service offerings are mapped correctly. Service blueprints in Terremark are compute-pool specific.
LDC search list does not display all environments and compute pools
The LDC search list does not display all environments and compute pools from registered Terremark accounts.
To workaround this issue:
- Check accounts registered for correctness. This occurs when the credentials provided for an account are incorrect.
- Restart Platform Manager services.
Installation of software fails
If the installation of software fails, you must check for correct versions of the RSCD agent in the custom template and BMC Server Automation. Execute the job from the BMC Server Automation console to check for possible errors in job configuration.
While provisioning multiple VMs, some of the VMs fail to provision
While provisioning multiple VMs, some of the VMs fail to provision.
To workaround this issue, edit the provider details and update poll counts. You must also check with Terremark support for issues related to SSH customization or when the infrastructure capacity available in the Terremark account is exhausted.