New VMs stuck in LCM_INIT state

Community Support
1

Our long-lasting OpenNebula environment has recently started to have this issue:

As the title states, deployments get stuck in LCM_INIT state, right before communicating the scheduler decission to the selected host

image
image676×110 5.25 KB

Logs are the expected in this phase of the deployment process
image

image
image1036×546 27 KB

Our setup uses 3 FrontEnd (virtualized) hosts running in HA mode. All of them have connectivity to all hosts, and have enough disk space and computing resources. The VIP is also in the right active FE.

Also, FEs can ssh the hosts without password using oneadmin user

image
image1154×824 44.9 KB

Our “temporal solution” to this issue has consisted on restarting opennebula in the active FE, and retrying everything again. This allows to use OpenNebula as normal for a while, but it is a temporal solution, as not long after it happens again

**Versions of the related components and OS (frontend, hypervisors, VMs):**Frontends in v6.10.2, hypervisors in v6.10.3

**Steps to reproduce:**Nothing weird, instancing a normal VM from any template

Current results: As show in the screenshot, VMs stuck in LCM_INIT state, and its imposible to delete them or restart the process

**Expected results:**VMs deploying correctly

2

Hello @Alvaro,

Welcome to this forum, hope we can help you out.

The first quick solution is to update your OpenNebula to 6.10 version, and check if the issue persists.

In the meantime, and since you already have the logs, have you tried to force synchronization of the hosts?. I will check with the team if we can give you some ideas about a potential solution.

Cheers,