[Issue description]
Customer tried to clone a Cloud host. The Procedure: Stop cloud host; More; Clone
![]()
The procedure ended in error. Cannot start or delete the cloning host. The host cloned was rai-gv-vip-01
![]()
[Version] FusionCloud 2.0.6 + FusionCompute(Xen)
![]()
[Analysis]
1. As other case, we checked the license of the storage. It contains HyperCopy license.
# Actually, the clone procedure has no error. No need to check this step.
![]()
2. By remote session, we try to check the VM in FusionCompute, but by ID of cloud host, we did not find the VM in FusionCompute. # don’t know the reason for the moment.
3. In CLI, login to the FusionSphere OpenStack Management Console IP with fsp account (default passwd is Huawei@CLOUD8). Run “su - root”, default passwd is Huawei@CLOUD8!). Run “source set_env”, intput “1”, and passwd “FusionSphere123”.
4. Run “nova show $ID”, $ID is the faulty cloud host. We can see, there is no IP for the VM, and copy its network ID.
![]()
5. Run the command “neutron net-show $network-ID” to get its subnet ID.
![]()
6. neutron port-list --network $sub-network-id, to get its IP range, which is 10.4.9.146-150
![]()
7. neutron port-list | grep 10.9.14, and neutron port-list | grep 10.9.150. we can see the all IPs are used by other VMs, and there is no available IP for new VMs. Now we find the root cause.
8. After the customer add more IPs in the subnet, clone made successfully.
![]()
![]()
9. Besides, the customer cannot delete the two faulty VMs in portal, we use the below two commands to delete them one by one.
1) nova reset-state vm-id --active
2) nova delete vm-id