[ovirt-users] Re: VM stuck in reboot

2021-02-14 Thread Arik Hadas 
On Fri, Feb 12, 2021 at 7:51 PM Michael Schmid 
wrote:

> 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
>
I'm glad to see it helped :)
I tried to reproduce it by invoking shutdown and reboot simultaneously but
it didn't happen to me with 4.4.4 so I tend to think you've encountered
https://bugzilla.redhat.com/show_bug.cgi?id=1880251 with the previous
version. If it happens again, please let us know.

> Mike
>
> On 2/12/2021 11:52 AM, Arik Hadas wrote:
>
>
>
> On Fri, Feb 12, 2021 at 4:44 PM Michael Schmid 
> 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-le...@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/
>>
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/PZPRTQXHU4WAZSWKXHMFCUYVUOGFNACG/

[ovirt-users] Re: VM stuck in reboot

2021-02-12 Thread Michael Schmid 
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

Email Sig
On 2/12/2021 11:52 AM, Arik Hadas wrote:
>
>
> On Fri, Feb 12, 2021 at 4:44 PM Michael Schmid
> mailto:micha...@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-le...@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/
> 
> 
>


OpenPGP_0x00552F0455EC7825.asc
Description: application/pgp-keys


OpenPGP_signature
Description: OpenPGP digital signature
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/5UMVKCFMEJGKPJO2HJSSAWCNB5JV5LND/

[ovirt-users] Re: VM stuck in reboot

2021-02-12 Thread Arik Hadas 
On Fri, Feb 12, 2021 at 4:44 PM Michael Schmid 
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-le...@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/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/3JOSMTLBZVMSOXCGMK4NCVKXEVQFQLKH/

[ovirt-users] Re: VM stuck in "reboot in progress" ("virtual machine XXX should be running in a host but it isn't.").

2020-09-22 Thread Gilboa Davara 
Arik / Strahil,

Many thanks!

Just in-case anyone else is hitting the same issue (*NOTE* Host and VM
ID _will_ be different!)
0. Ran a backup:
1. Connect to the hosted-engine and DB:
$ ssh root@vmengine
$ su - postgres
$ psql engine
2. Execute a select query to verify that the VM's run_on_vds is NULL:
# select * from vm_dynamic where vm_guid='b411e573-bcda-4689-b61f-1811c6f03ad5';
3. Execute Arik's update query:
# update vm_dynamic set
run_on_vds='82f92946-9130-4dbd-8663-1ac0b50668a1' where
vm_guid='b411e573-bcda-4689-b61f-1811c6f03ad5';
4. Re-started the engine:
$ systemctl restart ovirt-engine
5. Everything seems fine now. Profit!

Thanks again,
Gilboa

On Mon, Sep 21, 2020 at 4:28 PM Arik Hadas  wrote:
>
>
>
> On Sun, Sep 20, 2020 at 11:21 AM Gilboa Davara  wrote:
>>
>> On Sat, Sep 19, 2020 at 7:44 PM Arik Hadas  wrote:
>> >
>> >
>> >
>> > On Fri, Sep 18, 2020 at 8:27 AM Gilboa Davara  wrote:
>> >>
>> >> Hello all (and happy new year),
>> >>
>> >> (Note: Also reported as 
>> >> https://bugzilla.redhat.com/show_bug.cgi?id=1880251)
>> >>
>> >> Self hosted engine, single node, NFS.
>> >> Attempted to install CentOS over an existing Fedora VM with one host
>> >> device (USB printer).
>> >> Reboot failed, trying to boot from a non-existent CDROM.
>> >> Tried shutting the VM down, failed.
>> >> Tried powering off the VM, failed.
>> >> Dropped cluster to global maintenance, reboot host + engine (was
>> >> planning to upgrade it anyhow...), VM still stuck.
>> >>
>> >> When trying to power off the VM, the following message can be found
>> >> the in engine.log:
>> >> 2020-09-18 07:58:51,439+03 INFO
>> >> [org.ovirt.engine.core.bll.StopVmCommand]
>> >> (EE-ManagedThreadFactory-engine-Thread-42)
>> >> [7bc4ac71-f0b2-4af7-b081-100dc99b6123] Running command: StopVmCommand
>> >> internal: false. Entities affected :  ID:
>> >> b411e573-bcda-4689-b61f-1811c6f03ad5 Type: VMAction group STOP_VM with
>> >> role type USER
>> >> 2020-09-18 07:58:51,441+03 WARN
>> >> [org.ovirt.engine.core.bll.StopVmCommand]
>> >> (EE-ManagedThreadFactory-engine-Thread-42)
>> >> [7bc4ac71-f0b2-4af7-b081-100dc99b6123] Strange, according to the
>> >> status 'RebootInProgress' virtual machine
>> >> 'b411e573-bcda-4689-b61f-1811c6f03ad5' should be running in a host but
>> >> it isn't.
>> >> 2020-09-18 07:58:51,594+03 ERROR
>> >> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
>> >> (EE-ManagedThreadFactory-engine-Thread-42)
>> >> [7bc4ac71-f0b2-4af7-b081-100dc99b6123] EVENT_ID:
>> >> USER_FAILED_STOP_VM(56), Failed to power off VM kids-home-srv (Host:
>> >> , User: gilboa@internal-authz).
>> >>
>> >> My question is simple: Pending a solution to the bug, can I somehow
>> >> drop the state of the VM? It's currently holding a sizable disk image
>> >> and a USB device I need (printer).
>> >
>> >
>> > It would be best to modify the VM as if it should still be running on the 
>> > host and let the system discover that it's not running there and update 
>> > the VM accordingly.
>> >
>> > You can do it by changing the database with:
>> > update vm_dynamic set run_on_vds='82f92946-9130-4dbd-8663-1ac0b50668a1' 
>> > where vm_guid='b411e573-bcda-4689-b61f-1811c6f03ad5';
>> >
>> >
>> >>
>> >>
>> >> As it's my private VM cluster, I have no problem dropping the site
>> >> completely for maintenance.
>> >>
>> >> Thanks,
>> >>
>> >> Gilboa
>>
>>
>> Hello,
>>
>> Thanks for the prompt answer.
>>
>> Edward,
>>
>> Full reboot of both engine and host didn't help.
>> Most likely there's a consistency problem in the oVirt DB.
>>
>> Arik,
>>
>> To which DB I should connect and as which user?
>> E.g. psql -U user db_name
>
>
> To the 'engine' database.
> I usually connect to it by switching to the 'postgres' user as Strahil 
> described.
>
>>
>>
>> Thanks again,
>> - Gilboa
>>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/UVUOGUI7N3AW2L4J2WCQBQUW4BTTCOA6/

[ovirt-users] Re: VM stuck in "reboot in progress" ("virtual machine XXX should be running in a host but it isn't.").

2020-09-21 Thread Arik Hadas 
On Sun, Sep 20, 2020 at 11:21 AM Gilboa Davara  wrote:

> On Sat, Sep 19, 2020 at 7:44 PM Arik Hadas  wrote:
> >
> >
> >
> > On Fri, Sep 18, 2020 at 8:27 AM Gilboa Davara  wrote:
> >>
> >> Hello all (and happy new year),
> >>
> >> (Note: Also reported as
> https://bugzilla.redhat.com/show_bug.cgi?id=1880251)
> >>
> >> Self hosted engine, single node, NFS.
> >> Attempted to install CentOS over an existing Fedora VM with one host
> >> device (USB printer).
> >> Reboot failed, trying to boot from a non-existent CDROM.
> >> Tried shutting the VM down, failed.
> >> Tried powering off the VM, failed.
> >> Dropped cluster to global maintenance, reboot host + engine (was
> >> planning to upgrade it anyhow...), VM still stuck.
> >>
> >> When trying to power off the VM, the following message can be found
> >> the in engine.log:
> >> 2020-09-18 07:58:51,439+03 INFO
> >> [org.ovirt.engine.core.bll.StopVmCommand]
> >> (EE-ManagedThreadFactory-engine-Thread-42)
> >> [7bc4ac71-f0b2-4af7-b081-100dc99b6123] Running command: StopVmCommand
> >> internal: false. Entities affected :  ID:
> >> b411e573-bcda-4689-b61f-1811c6f03ad5 Type: VMAction group STOP_VM with
> >> role type USER
> >> 2020-09-18 07:58:51,441+03 WARN
> >> [org.ovirt.engine.core.bll.StopVmCommand]
> >> (EE-ManagedThreadFactory-engine-Thread-42)
> >> [7bc4ac71-f0b2-4af7-b081-100dc99b6123] Strange, according to the
> >> status 'RebootInProgress' virtual machine
> >> 'b411e573-bcda-4689-b61f-1811c6f03ad5' should be running in a host but
> >> it isn't.
> >> 2020-09-18 07:58:51,594+03 ERROR
> >> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> >> (EE-ManagedThreadFactory-engine-Thread-42)
> >> [7bc4ac71-f0b2-4af7-b081-100dc99b6123] EVENT_ID:
> >> USER_FAILED_STOP_VM(56), Failed to power off VM kids-home-srv (Host:
> >> , User: gilboa@internal-authz).
> >>
> >> My question is simple: Pending a solution to the bug, can I somehow
> >> drop the state of the VM? It's currently holding a sizable disk image
> >> and a USB device I need (printer).
> >
> >
> > It would be best to modify the VM as if it should still be running on
> the host and let the system discover that it's not running there and update
> the VM accordingly.
> >
> > You can do it by changing the database with:
> > update vm_dynamic set run_on_vds='82f92946-9130-4dbd-8663-1ac0b50668a1'
> where vm_guid='b411e573-bcda-4689-b61f-1811c6f03ad5';
> >
> >
> >>
> >>
> >> As it's my private VM cluster, I have no problem dropping the site
> >> completely for maintenance.
> >>
> >> Thanks,
> >>
> >> Gilboa
>
>
> Hello,
>
> Thanks for the prompt answer.
>
> Edward,
>
> Full reboot of both engine and host didn't help.
> Most likely there's a consistency problem in the oVirt DB.
>
> Arik,
>
> To which DB I should connect and as which user?
> E.g. psql -U user db_name
>

To the 'engine' database.
I usually connect to it by switching to the 'postgres' user as Strahil
described.


>
> Thanks again,
> - Gilboa
>
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/Z3NF7BKSZFBPZ6ZIN6PICTXJVO3A4Q3A/

[ovirt-users] Re: VM stuck in "reboot in progress" ("virtual machine XXX should be running in a host but it isn't.").

2020-09-20 Thread Strahil Nikolov via Users 
Ah , host is treated as operational (Active)...
I guess you can check the status of the VM in the engine , but keep in mind 
that direct manipulation of the DB is highly not recommended (but desperate 
people require desperate measures).

Usually I ssh to the HE as root:
ssh root@HE
su - postgres
source /opt/rh/rh-postgresql10/enable
psql engine

List the tables:
\dt

Then you have to search where the status of the VM is.

Best Regards,
Strahil Nikolov






В неделя, 20 септември 2020 г., 11:59:53 Гринуич+3, Gilboa Davara 
 написа: 





On Sat, Sep 19, 2020 at 5:07 PM Strahil Nikolov  wrote:>
> You have rebooted the host where the VM was previously running , right ?
> If oVirt doesn't detect that the host was rebooted , you can mark it as such :
> UI -> Hosts -> select the Host -> the 3 dots -> "Confirm 'Host has been 
> rebooted'"
>
> Best Regards,
> Strahil Nikolov
>

"Confirm host was rebooted" fails when host is up.
The error message is: '"Error while executing action: Cannot confirm
'Host has been rebooted' Host. Valid Host statuses are "Non
operational", "Maintenance" or "Connecting"'.


- Gilboa
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/6NUVSN3UFBRWWPTPRTEMLOYD2FZ4/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/DP3WYZO5CTRPL52GTUMO4E42U67BIKSE/

[ovirt-users] Re: VM stuck in "reboot in progress" ("virtual machine XXX should be running in a host but it isn't.").

2020-09-20 Thread Gilboa Davara 
On Sat, Sep 19, 2020 at 5:07 PM Strahil Nikolov  wrote:>
> You have rebooted the host where the VM was previously running , right ?
> If oVirt doesn't detect that the host was rebooted , you can mark it as such :
> UI -> Hosts -> select the Host -> the 3 dots -> "Confirm 'Host has been 
> rebooted'"
>
> Best Regards,
> Strahil Nikolov
>

"Confirm host was rebooted" fails when host is up.
The error message is: '"Error while executing action: Cannot confirm
'Host has been rebooted' Host. Valid Host statuses are "Non
operational", "Maintenance" or "Connecting"'.

- Gilboa
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/6NUVSN3UFBRWWPTPRTEMLOYD2FZ4/

[ovirt-users] Re: VM stuck in "reboot in progress" ("virtual machine XXX should be running in a host but it isn't.").

2020-09-20 Thread Gilboa Davara 
On Sat, Sep 19, 2020 at 7:44 PM Arik Hadas  wrote:
>
>
>
> On Fri, Sep 18, 2020 at 8:27 AM Gilboa Davara  wrote:
>>
>> Hello all (and happy new year),
>>
>> (Note: Also reported as https://bugzilla.redhat.com/show_bug.cgi?id=1880251)
>>
>> Self hosted engine, single node, NFS.
>> Attempted to install CentOS over an existing Fedora VM with one host
>> device (USB printer).
>> Reboot failed, trying to boot from a non-existent CDROM.
>> Tried shutting the VM down, failed.
>> Tried powering off the VM, failed.
>> Dropped cluster to global maintenance, reboot host + engine (was
>> planning to upgrade it anyhow...), VM still stuck.
>>
>> When trying to power off the VM, the following message can be found
>> the in engine.log:
>> 2020-09-18 07:58:51,439+03 INFO
>> [org.ovirt.engine.core.bll.StopVmCommand]
>> (EE-ManagedThreadFactory-engine-Thread-42)
>> [7bc4ac71-f0b2-4af7-b081-100dc99b6123] Running command: StopVmCommand
>> internal: false. Entities affected :  ID:
>> b411e573-bcda-4689-b61f-1811c6f03ad5 Type: VMAction group STOP_VM with
>> role type USER
>> 2020-09-18 07:58:51,441+03 WARN
>> [org.ovirt.engine.core.bll.StopVmCommand]
>> (EE-ManagedThreadFactory-engine-Thread-42)
>> [7bc4ac71-f0b2-4af7-b081-100dc99b6123] Strange, according to the
>> status 'RebootInProgress' virtual machine
>> 'b411e573-bcda-4689-b61f-1811c6f03ad5' should be running in a host but
>> it isn't.
>> 2020-09-18 07:58:51,594+03 ERROR
>> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
>> (EE-ManagedThreadFactory-engine-Thread-42)
>> [7bc4ac71-f0b2-4af7-b081-100dc99b6123] EVENT_ID:
>> USER_FAILED_STOP_VM(56), Failed to power off VM kids-home-srv (Host:
>> , User: gilboa@internal-authz).
>>
>> My question is simple: Pending a solution to the bug, can I somehow
>> drop the state of the VM? It's currently holding a sizable disk image
>> and a USB device I need (printer).
>
>
> It would be best to modify the VM as if it should still be running on the 
> host and let the system discover that it's not running there and update the 
> VM accordingly.
>
> You can do it by changing the database with:
> update vm_dynamic set run_on_vds='82f92946-9130-4dbd-8663-1ac0b50668a1' where 
> vm_guid='b411e573-bcda-4689-b61f-1811c6f03ad5';
>
>
>>
>>
>> As it's my private VM cluster, I have no problem dropping the site
>> completely for maintenance.
>>
>> Thanks,
>>
>> Gilboa


Hello,

Thanks for the prompt answer.

Edward,

Full reboot of both engine and host didn't help.
Most likely there's a consistency problem in the oVirt DB.

Arik,

To which DB I should connect and as which user?
E.g. psql -U user db_name

Thanks again,
- Gilboa
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/XUFMFHGE5U4ICTBMSBN4TRW74KRGDIIS/

[ovirt-users] Re: VM stuck in "reboot in progress" ("virtual machine XXX should be running in a host but it isn't.").

2020-09-19 Thread Arik Hadas 
On Fri, Sep 18, 2020 at 8:27 AM Gilboa Davara  wrote:

> Hello all (and happy new year),
>
> (Note: Also reported as
> https://bugzilla.redhat.com/show_bug.cgi?id=1880251)
>
> Self hosted engine, single node, NFS.
> Attempted to install CentOS over an existing Fedora VM with one host
> device (USB printer).
> Reboot failed, trying to boot from a non-existent CDROM.
> Tried shutting the VM down, failed.
> Tried powering off the VM, failed.
> Dropped cluster to global maintenance, reboot host + engine (was
> planning to upgrade it anyhow...), VM still stuck.
>
> When trying to power off the VM, the following message can be found
> the in engine.log:
> 2020-09-18 07:58:51,439+03 INFO
> [org.ovirt.engine.core.bll.StopVmCommand]
> (EE-ManagedThreadFactory-engine-Thread-42)
> [7bc4ac71-f0b2-4af7-b081-100dc99b6123] Running command: StopVmCommand
> internal: false. Entities affected :  ID:
> b411e573-bcda-4689-b61f-1811c6f03ad5 Type: VMAction group STOP_VM with
> role type USER
> 2020-09-18 07:58:51,441+03 WARN
> [org.ovirt.engine.core.bll.StopVmCommand]
> (EE-ManagedThreadFactory-engine-Thread-42)
> [7bc4ac71-f0b2-4af7-b081-100dc99b6123] Strange, according to the
> status 'RebootInProgress' virtual machine
> 'b411e573-bcda-4689-b61f-1811c6f03ad5' should be running in a host but
> it isn't.
> 2020-09-18 07:58:51,594+03 ERROR
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (EE-ManagedThreadFactory-engine-Thread-42)
> [7bc4ac71-f0b2-4af7-b081-100dc99b6123] EVENT_ID:
> USER_FAILED_STOP_VM(56), Failed to power off VM kids-home-srv (Host:
> , User: gilboa@internal-authz).
>
> My question is simple: Pending a solution to the bug, can I somehow
> drop the state of the VM? It's currently holding a sizable disk image
> and a USB device I need (printer).
>

It would be best to modify the VM as if it should still be running on the
host and let the system discover that it's not running there and update the
VM accordingly.

You can do it by changing the database with:
update vm_dynamic set run_on_vds='82f92946-9130-4dbd-8663-1ac0b50668a1'
where vm_guid='b411e573-bcda-4689-b61f-1811c6f03ad5';



>
> As it's my private VM cluster, I have no problem dropping the site
> completely for maintenance.
>
> Thanks,
>
> Gilboa
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@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/CD536K6HHE5JX7QY2DA6LYNTFABLYR2K/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/7JR22MIXFN7FCLOCZB3AW5DQXGHUZASK/

[ovirt-users] Re: VM stuck in "reboot in progress" ("virtual machine XXX should be running in a host but it isn't.").

2020-09-19 Thread Edward Berger 
I've had situations where the engine UI wouldn't update for
shutdown/startups of VMs which were resolved after ssh-ing into the engine
VM and running systemctl restart ovirt-engine.service.  running
engine-setup was also used on occasion and cleared out old tasks.

On Fri, Sep 18, 2020 at 1:26 AM Gilboa Davara  wrote:

> Hello all (and happy new year),
>
> (Note: Also reported as
> https://bugzilla.redhat.com/show_bug.cgi?id=1880251)
>
> Self hosted engine, single node, NFS.
> Attempted to install CentOS over an existing Fedora VM with one host
> device (USB printer).
> Reboot failed, trying to boot from a non-existent CDROM.
> Tried shutting the VM down, failed.
> Tried powering off the VM, failed.
> Dropped cluster to global maintenance, reboot host + engine (was
> planning to upgrade it anyhow...), VM still stuck.
>
> When trying to power off the VM, the following message can be found
> the in engine.log:
> 2020-09-18 07:58:51,439+03 INFO
> [org.ovirt.engine.core.bll.StopVmCommand]
> (EE-ManagedThreadFactory-engine-Thread-42)
> [7bc4ac71-f0b2-4af7-b081-100dc99b6123] Running command: StopVmCommand
> internal: false. Entities affected :  ID:
> b411e573-bcda-4689-b61f-1811c6f03ad5 Type: VMAction group STOP_VM with
> role type USER
> 2020-09-18 07:58:51,441+03 WARN
> [org.ovirt.engine.core.bll.StopVmCommand]
> (EE-ManagedThreadFactory-engine-Thread-42)
> [7bc4ac71-f0b2-4af7-b081-100dc99b6123] Strange, according to the
> status 'RebootInProgress' virtual machine
> 'b411e573-bcda-4689-b61f-1811c6f03ad5' should be running in a host but
> it isn't.
> 2020-09-18 07:58:51,594+03 ERROR
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (EE-ManagedThreadFactory-engine-Thread-42)
> [7bc4ac71-f0b2-4af7-b081-100dc99b6123] EVENT_ID:
> USER_FAILED_STOP_VM(56), Failed to power off VM kids-home-srv (Host:
> , User: gilboa@internal-authz).
>
> My question is simple: Pending a solution to the bug, can I somehow
> drop the state of the VM? It's currently holding a sizable disk image
> and a USB device I need (printer).
>
> As it's my private VM cluster, I have no problem dropping the site
> completely for maintenance.
>
> Thanks,
>
> Gilboa
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@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/CD536K6HHE5JX7QY2DA6LYNTFABLYR2K/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/QS7WZSPUL26GQUJFLNZXCAGD4PJJSG2B/

[ovirt-users] Re: VM stuck in "reboot in progress" ("virtual machine XXX should be running in a host but it isn't.").

2020-09-19 Thread Strahil Nikolov via Users 
You have rebooted the host where the VM was previously running , right ?
If oVirt doesn't detect that the host was rebooted , you can mark it as such :
UI -> Hosts -> select the Host -> the 3 dots -> "Confirm 'Host has been 
rebooted'"

Best Regards,
Strahil Nikolov






В петък, 18 септември 2020 г., 08:27:33 Гринуич+3, Gilboa Davara 
 написа: 





Hello all (and happy new year),

(Note: Also reported as https://bugzilla.redhat.com/show_bug.cgi?id=1880251)

Self hosted engine, single node, NFS.
Attempted to install CentOS over an existing Fedora VM with one host
device (USB printer).
Reboot failed, trying to boot from a non-existent CDROM.
Tried shutting the VM down, failed.
Tried powering off the VM, failed.
Dropped cluster to global maintenance, reboot host + engine (was
planning to upgrade it anyhow...), VM still stuck.

When trying to power off the VM, the following message can be found
the in engine.log:
2020-09-18 07:58:51,439+03 INFO
[org.ovirt.engine.core.bll.StopVmCommand]
(EE-ManagedThreadFactory-engine-Thread-42)
[7bc4ac71-f0b2-4af7-b081-100dc99b6123] Running command: StopVmCommand
internal: false. Entities affected :  ID:
b411e573-bcda-4689-b61f-1811c6f03ad5 Type: VMAction group STOP_VM with
role type USER
2020-09-18 07:58:51,441+03 WARN
[org.ovirt.engine.core.bll.StopVmCommand]
(EE-ManagedThreadFactory-engine-Thread-42)
[7bc4ac71-f0b2-4af7-b081-100dc99b6123] Strange, according to the
status 'RebootInProgress' virtual machine
'b411e573-bcda-4689-b61f-1811c6f03ad5' should be running in a host but
it isn't.
2020-09-18 07:58:51,594+03 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(EE-ManagedThreadFactory-engine-Thread-42)
[7bc4ac71-f0b2-4af7-b081-100dc99b6123] EVENT_ID:
USER_FAILED_STOP_VM(56), Failed to power off VM kids-home-srv (Host:
, User: gilboa@internal-authz).

My question is simple: Pending a solution to the bug, can I somehow
drop the state of the VM? It's currently holding a sizable disk image
and a USB device I need (printer).

As it's my private VM cluster, I have no problem dropping the site
completely for maintenance.

Thanks,

Gilboa
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/CD536K6HHE5JX7QY2DA6LYNTFABLYR2K/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/WCSLZX3STLTTVYMYPWIOFVVPDYP4OVFZ/

[ovirt-users] Re: VM stuck in "reboot in progress" ("virtual machine XXX should be running in a host but it isn't.").

2020-09-17 Thread Gilboa Davara 
P.S. Full engine log attached to the bugzilla entry.

- Gilboa

On Fri, Sep 18, 2020 at 8:23 AM Gilboa Davara  wrote:
>
> Hello all (and happy new year),
>
> (Note: Also reported as https://bugzilla.redhat.com/show_bug.cgi?id=1880251)
>
> Self hosted engine, single node, NFS.
> Attempted to install CentOS over an existing Fedora VM with one host
> device (USB printer).
> Reboot failed, trying to boot from a non-existent CDROM.
> Tried shutting the VM down, failed.
> Tried powering off the VM, failed.
> Dropped cluster to global maintenance, reboot host + engine (was
> planning to upgrade it anyhow...), VM still stuck.
>
> When trying to power off the VM, the following message can be found
> the in engine.log:
> 2020-09-18 07:58:51,439+03 INFO
> [org.ovirt.engine.core.bll.StopVmCommand]
> (EE-ManagedThreadFactory-engine-Thread-42)
> [7bc4ac71-f0b2-4af7-b081-100dc99b6123] Running command: StopVmCommand
> internal: false. Entities affected :  ID:
> b411e573-bcda-4689-b61f-1811c6f03ad5 Type: VMAction group STOP_VM with
> role type USER
> 2020-09-18 07:58:51,441+03 WARN
> [org.ovirt.engine.core.bll.StopVmCommand]
> (EE-ManagedThreadFactory-engine-Thread-42)
> [7bc4ac71-f0b2-4af7-b081-100dc99b6123] Strange, according to the
> status 'RebootInProgress' virtual machine
> 'b411e573-bcda-4689-b61f-1811c6f03ad5' should be running in a host but
> it isn't.
> 2020-09-18 07:58:51,594+03 ERROR
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (EE-ManagedThreadFactory-engine-Thread-42)
> [7bc4ac71-f0b2-4af7-b081-100dc99b6123] EVENT_ID:
> USER_FAILED_STOP_VM(56), Failed to power off VM kids-home-srv (Host:
> , User: gilboa@internal-authz).
>
> My question is simple: Pending a solution to the bug, can I somehow
> drop the state of the VM? It's currently holding a sizable disk image
> and a USB device I need (printer).
>
> As it's my private VM cluster, I have no problem dropping the site
> completely for maintenance.
>
> Thanks,
>
> Gilboa
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/IOCPXQJ3RKE3SZAELLGNWNXQCA4YWPH4/