problem | possible cause | try this |
---|---|---|
vApp create operation failed. After uploading the VMDK, you see the error: "Timeout waiting for start completion" | Platform Manager is unable to connect to the Virtual Machine (VM). | From the VMware vSphere console, login to the VM and confirm that it has IP addresses on all expected interfaces. If any IP addresses are missing, open the /var/log/messages folder, and search for the phrase “some other host already uses address”. This phrase indicates an address conflict. If no IP conflict is found, confirm that: 1) Platform Manager is in the same network as the VMThe resource blueprint defines the new machine’s Remote Networks property. 2) The MSL remote networks on the VM will allow the Platform Manager network to connect. |
vApp create operation failed. When you look at the vSphere console for the new VM, you see a blue MSL screen with an interface error or the error message: "An error occurred during restore". | IP address conflict. | See the solution for the previous problem, above. |
vApp create operation failed. You see the error message: “failed due to OAuth error” | IP address conflict. | Platform Manager was unable to connect to the VM. Confirm that it has started. Look at the VM console via VMware vSphere console. See IP address solutions above. Confirm that the server has properly started. Open /var/log/messages and work back from the bottom. Confirm that PostgreSQL (psql) started. |
vApp create operation failed from blueprint that has an MSL golden database. You see an error message like: OAuth, unable to login to server at xx.xx.xx.xx. Confirm that MSL password is correct. | Incorrect MSL admin password. | The MSL admin password that was entered in the resource blueprint is not the same as the MSL password that is in the golden database. After the restore, the MSL password will match the one in the restored db. |