Hello, community members.
Today I’m going to introduce you how to deal with failed to create VM on FusionCloud.
We all know how to create a VM. Of course, the creation method is relatively simple.
We have encountered creation failures because there are too many failure cases. I think you are also worried about this.
Today, I'd like to share with you how to deal with Failed to create VM on FusionCloud.
Problem Description
Fusioncloud 2.0.6 creates VM failed and there is a license expired alarm on fusioncompute.

Problem Analysis
For FusionCloud 2.0.6 scene, the FusionCompute obtain the license from FusionSphere OpenStack OM, and we found that the license synchronization failed from OM to FusionCompute.

Finally, we found that the cause connection failure between OM and FusionCompute is that the gmsysman account password incorrect.

Root Cause
The gmsysman account is for communication with OM and FusionCompute, the password has been changed only on FusionCompute but not on OM.
Solution Description
Make sure the gmsysman account password is the same on FusionCompute and OM.
That's all for today. I hope it will be helpful to all of you!
If you have any other comments or want to know more, please leave a message below to let me know.



