Hi,
I have OpenNebula 5.0.1 with 9 nodes. The OS in all the servers is Ubuntu 14 server and the hypervisor of the nodes is KVM.
My problem is that in one of the nodes I cannot deploy any VM because it stucks on boot state and nothing changes.
I deployed a MV in that node with virsh by command line and it seems to work fine.
On the other hand, oned.log only shows that the current state is the generation of the deploymen file.
Thank you very much, best regards.
Have you checked passwordless oneadmin ssh access from opennebula front-end to this host?
It would be better to see more information: ds type, is there any logs in VM’s log file (/var/log/one/.log on the opennebula front-end server, not on the host) and so on?
Yes, oneadmin passwordless between the node and the front-end is fine.
Some of the last lines of a VM log (front-end) which stucks on boot are the following ones:
Mon Nov 13 09:47:01 2017 [Z0][VMM][I]: Generating deployment file: /var/lib/one/vms/932/deployment.6
Wed Nov 15 14:06:08 2017 [Z0][VM][I]: New LCM state is RUNNING
Wed Nov 15 14:06:15 2017 [Z0][LCM][I]: VM running but monitor state is POWEROFF
Wed Nov 15 14:06:15 2017 [Z0][VM][I]: New LCM state is SHUTDOWN_POWEROFF
Wed Nov 15 14:06:15 2017 [Z0][VM][I]: New state is POWEROFF
Wed Nov 15 14:06:15 2017 [Z0][VM][I]: New LCM state is LCM_INIT
Wed Nov 15 14:06:29 2017 [Z0][VM][I]: New state is ACTIVE
Wed Nov 15 14:06:29 2017 [Z0][VM][I]: New LCM state is BOOT_POWEROFF
Wed Nov 15 14:06:29 2017 [Z0][VMM][I]: Generating deployment file: /var/lib/one/vms/932/deployment.7
The RUNNING states are because of the retry option, so that I can migrate the VM.
On the other hand, oned.log doesn’t show anything.
Thank you very much.