Arik,

Thank you so much, that solved it.

that was my updates/maintenance weekend, so I would have probably updated the cluster at the same time. I'm not sure of the order I was trying to go home.

I am so sorry I didn't find the previous post before asking

Thank you again

Mike

On Fri, Feb 12, 2021 at 4:44 PM Michael Schmid <michaels@teampiedmont.com> wrote:

Hi All,

I am running on 4.4.4.7-1.el8

I messed up. I was doing some weekend maintenance on VMs and some VMs
needed to be stopped and some rebooted and I stopped one, thought I
clicked on the next one and clicked shutdown. But... I clicked reboot
and shutdown on the same VM, now it is stuck. The Overview in the engine
shows the VM "Reboot In Progress" and it has for two weeks at this
point, it was a fresh VM so I just created a new one until I had this
figured out, but here I am. Clicking "Shutdown" does nothing but
generate an error, same with "Power Off" the error I get is

---

2021-02-10 12:04:03,460-05 INFO 
[org.ovirt.engine.core.bll.StopVmCommand]
(EE-ManagedThreadFactory-engine-Thread-244169)
[c3ce0a41-3f53-4f3e-993f-0d75f62cc8e6] Running command: StopVmCommand
internal: false. Entities affected :  ID:
d4e90edd-0598-4ac1-b814-2cae8d29e216 Type: VMAction group STOP_VM with
role type USER
2021-02-10 12:04:03,464-05 WARN 
[org.ovirt.engine.core.bll.StopVmCommand]
(EE-ManagedThreadFactory-engine-Thread-244169)
[c3ce0a41-3f53-4f3e-993f-0d75f62cc8e6] Strange, according to the status
'RebootInProgress' virtual machine
'd4e90edd-0598-4ac1-b814-2cae8d29e216' should be running in a host but
it isn't.
2021-02-10 12:04:03,485-05 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(EE-ManagedThreadFactory-engine-Thread-244169)
[c3ce0a41-3f53-4f3e-993f-0d75f62cc8e6] EVENT_ID:
USER_FAILED_STOP_VM(56), Failed to power off VM snipeit

---

I have shut down the entire system. all VMs the hosts, the engine, and
nothing changes. still stuck in reboot in progress

I would greatly appreciate any help

You'll need to make a change in the database, see [1].

This really shouldn't happen with 4.4.4.7 though.

You say the VM is in this state for two weeks, right? Can it be that it got to that state before you've upgraded to 4.4.4?

[1] https://www.mail-archive.com/users@ovirt.org/msg62928.html

 

Thanks

Mike


_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/IQ2YNJSNWANRUFIJHC5O2JD63M7FSBEW/