Recovering Virtual Guests in “Unknown” status after losing access to storage
You must reset the VMs state into database to recover it from “Unknown” status . Thanks [1]
1. If VMs with unknown state still works - shutdown it normally.
You must shutdown VMs to prevent data lose.
2. Connect to engine PostgreSQL database.
3. Grab the VM GUID
# SELECT vm_guid from vm_static WHERE vm_name='server01-examplecom';
4. Set the status of virtual guest to a status of “0”
# UPDATE vm_dynamic SET status=0 WHERE vm_guid='df13ca7f-b6fa-4820-8a7b-28d785221b64';
[1] - https://www.dalemacartney.com/2013/02/17/recovering-rhev-virtual-guests-in-unknown-status-after-losing-access-to-storage/
01.04.2020, 20:49, "Mark Steele" <mste...@telvue.com>:
A million years ago - we are going to be upgrading with a new cluster but for now, we have this one.It's production and we cannot take it down unless absolutely necessary.***Mark SteeleCIO / VP Technical Operations | TelVue CorporationTelVue - We Share Your Vision16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054800.885.8886 | mste...@telvue.com | http://www.telvue.com,On Wed, Apr 1, 2020 at 1:17 PM Strahil Nikolov <hunter86...@yahoo.com> wrote:On April 1, 2020 5:40:27 PM GMT+03:00, Mark Steele <mste...@telvue.com> wrote:
>Two other symptoms:
>
>- Some of the HV's respond 'Destination Host Prohibited' on ping, but
>SSH
>works fine
>
>- Seeing this in the log:
>
>2020-04-01 10:34:31,839 ERROR
>[org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor)
>Unable to process messages: javax.net.ssl.SSLException: Received fatal
>alert: certificate_expired
>
>
>***
>*Mark Steele*
>CIO / VP Technical Operations | TelVue Corporation
>TelVue - We Share Your Vision
>16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054
>800.885.8886 | mste...@telvue.com | http://www.telvue.com
>twitter: http://twitter.com/telvue | facebook:
>https://www.facebook.com/telvue
>
>
>On Wed, Apr 1, 2020 at 10:25 AM Mark Steele <mste...@telvue.com> wrote:
>
>> Yesterday we had a storage crash that caused our hosted engine to
>stop and
>> not auto-restart. We manually restarted it and this morning, all
>elements
>> are showing a status of either question mark '?' or a red down
>chevron.
>>
>> We are running version oVirt Engine Version: 3.5.0.1-1.el6.
>>
>> We are chasing it down and see this in the log:
>>
>> 2020-04-01 10:15:53,060 WARN
>[org.ovirt.engine.core.vdsbroker.VdsManager]
>(DefaultQuartzScheduler_Worker-23) Failed to refresh VDS , vds =
>e98f8f1d-dd1d-47c4-b039-d6eaaf578317 : hv-06, VDS Network Error,
>continuing
>>
>>
>> Any insight into what might be causing this or the fix would be
>> appreciated.
>>
>> ***
>> *Mark Steele*
>>
>>
Hey Mark,
When was the oVirt last updated ?
Best Regards,
Strahil Nikolov_______________________________________________
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/R2XCPOELMPS2VRAMWQ756J4EJD7TI2VE/
_______________________________________________ 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/XXKA7XQGFFOV5YFW36QF7YJIWWCK3TNR/
