Hello,
After a long weekend,
I still have the problem
Can someone help me?
My log : After disable/enable zone
2022-06-07 09:26:45,809 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-2:ctx-1674af2a job-459203/job-487382 ctx-ebb9c3ea)
(logid:afa9332e) VM instance {id: "604", name: "s-604-VM", uuid:
"f3902827-fbc3-405c-a5e9-8666a904d9d3", type="SecondaryStorageVm"} state
transited from [Starting] to [Stopped] with event [OperationFailed].
VM's original host: null, new host: null, host before state transition: null
2022-06-07 09:26:45,809 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-1:ctx-6086fc4b job-458821/job-487381 ctx-2726829b)
(logid:2ec6e97d) VM instance {id: "603", name: "v-603-VM", uuid:
"4caaa2ff-a9dc-4708-aa7e-21b65b83f8e8", type="ConsoleProxy"} state
transited from [Starting] to [Stopped] with event [OperationFailed].
VM's original host: null, new host: null, host before state transition: null
2022-06-07 09:26:45,811 INFO [c.c.v.VirtualMachineManagerImpl]
(Work-Job-Executor-2:ctx-1674af2a job-459203/job-487382 ctx-ebb9c3ea)
(logid:afa9332e) Caught CloudRuntimeException, returning job failed
com.cloud.utils.exception.CloudRuntimeException: Unable to create
deployment, no usable volumes found for the VM: 604
2022-06-07 09:26:45,813 INFO [c.c.v.VirtualMachineManagerImpl]
(Work-Job-Executor-1:ctx-6086fc4b job-458821/job-487381 ctx-2726829b)
(logid:2ec6e97d) Caught CloudRuntimeException, returning job failed
com.cloud.utils.exception.CloudRuntimeException: Unable to create
deployment, no usable volumes found for the VM: 603
2022-06-07 09:26:45,828 DEBUG [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-1:ctx-6086fc4b job-458821/job-487381 ctx-2726829b)
(logid:2ec6e97d) Done executing VM work job:
com.cloud.vm.VmWorkStart{"dcId":0,"userId":1,"accountId":1,"vmId":603,"handlerName":"VirtualMachineManagerImpl"}
2022-06-07 09:26:45,828 DEBUG [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-2:ctx-1674af2a job-459203/job-487382 ctx-ebb9c3ea)
(logid:afa9332e) Done executing VM work job:
com.cloud.vm.VmWorkStart{"dcId":0,"userId":1,"accountId":1,"vmId":604,"handlerName":"VirtualMachineManagerImpl"}
Best regards,
Olivier
Le 04/06/2022 à 11:29, Olivier GUIN a écrit :
Hello,
Following an installability of my system, I had to delete the system VMs.
I put the zone in disable then delete the SSVMs and then I enable the
zone.
The ssvms have been created but in the Stopped state.
Here are the logs.
For information, I had not checked following my update from 4.15 to
4.16.1, but the ssvms were in 4.16.1 as well as all the virtual routers
Recurringly, when I restart the management server, its id changes?
which means that I have 2 controllers!I must change the msid in the
file in the host table (mgmt_server_id)!
Can you help me ?
2022-06-04 11:00:24,565 DEBUG [c.c.a.SecondaryStorageVmAlertAdapter]
(secstorage-1:ctx-54d121c3) (logid:040b79e7) received secondary
storage vm alert
2022-06-04 11:00:24,569 DEBUG [c.c.a.SecondaryStorageVmAlertAdapter]
(secstorage-1:ctx-54d121c3) (logid:040b79e7) Secondary Storage Vm
creation failure, zone: GF-CAY-01
2022-06-04 11:00:24,570 WARN [c.c.a.AlertManagerImpl]
(secstorage-1:ctx-54d121c3) (logid:040b79e7) alertType=[19]
dataCenterId=[1] podId=[null] clusterId=[null] message=[Secondary
Storage Vm creation failure. zone: GF-CAY-01, error details: Unable to
allocate capacity on zone [1] due to [null].].
2022-06-04 11:00:24,579 WARN [c.c.c.ConsoleProxyManagerImpl]
(consoleproxy-1:ctx-996e1b15) (logid:2f348c98) Unable to allocate
console proxy standby capacity for zone [1] due to [Unable to start VM
instance].
My conf :
- CentOS7 for Management
- Host : XCP-NG 7.6
Best regards,
Olivier
