<div dir="ltr">This is becoming critical for me, does anyone have any ideas or
recommendations on what I can do to recover access to hosted VM? As of
right now I have three hosts that are fully updated, they have the 4.2
repo and a full yum update was performed on them, there are no new
updates to apply. The hosted engine had updates as well as a full and
complete engine-setup, but did not return after being shut down. There
must be some way I can get the engine running again? Please</div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jan 11, 2018 at 8:24 AM, Jayme <span dir="ltr"><<a href="mailto:jaymef@gmail.com" target="_blank">jaymef@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">The hosts have all ready been fully updated with 4.2 packages though.<div><br></div><div>ex. </div><div><br></div><div><div>ovirt-host.x86_64 4.2.0-1.el7.centos @ovirt-4.2</div><div>ovirt-host-dependencies.x86_<wbr>64 4.2.0-1.el7.centos @ovirt-4.2</div><div>ovirt-host-deploy.noarch 1.7.0-1.el7.centos @ovirt-4.2</div><div>ovirt-hosted-engine-ha.noarch 2.2.2-1.el7.centos @ovirt-4.2</div><div>ovirt-hosted-engine-setup.<wbr>noarch 2.2.3-1.el7.centos @ovirt-4.2</div></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jan 11, 2018 at 8:16 AM, Martin Sivak <span dir="ltr"><<a href="mailto:msivak@redhat.com" target="_blank">msivak@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
yes, you need to upgrade the hosts. Just take the<br>
ovirt-hosted-engine-ha and ovirt-hosted-engine-setup packages from<br>
ovirt 4.2 repositories.<br>
<span class="m_6061824483285160243HOEnZb"><font color="#888888"><br>
Martin<br>
</font></span><div class="m_6061824483285160243HOEnZb"><div class="m_6061824483285160243h5"><br>
On Thu, Jan 11, 2018 at 11:40 AM, Jayme <<a href="mailto:jaymef@gmail.com" target="_blank">jaymef@gmail.com</a>> wrote:<br>
> How do I upgrade the hosted engine packages when I can't reach it or do you<br>
> mean upgrade the hosts if so how exactly do I do that. As for the missing VM<br>
> it appears that the disk image is there but it's missing XML file I have no<br>
> idea why or how to recreate it.<br>
><br>
> On Jan 11, 2018 4:43 AM, "Martin Sivak" <<a href="mailto:msivak@redhat.com" target="_blank">msivak@redhat.com</a>> wrote:<br>
>><br>
>> Hi,<br>
>><br>
>> you hit one known issue we already have fixes for (4.1 hosts with 4.2<br>
>> engine):<br>
>> <a href="https://gerrit.ovirt.org/#/q/status:open+project:ovirt-hosted-engine-ha+branch:v2.1.z+topic:ovf_42_for_41" rel="noreferrer" target="_blank">https://gerrit.ovirt.org/#/q/s<wbr>tatus:open+project:ovirt-hoste<wbr>d-engine-ha+branch:v2.1.z+<wbr>topic:ovf_42_for_41</a><br>
>><br>
>> You can try hotfixing it by upgrading hosted engine packages to 4.2 or<br>
>> applying the patches manually and installing python-lxml.<br>
>><br>
>> I am not sure what happened to your other VM.<br>
>><br>
>> Best regards<br>
>><br>
>> Martin Sivak<br>
>><br>
>> On Thu, Jan 11, 2018 at 6:15 AM, Jayme <<a href="mailto:jaymef@gmail.com" target="_blank">jaymef@gmail.com</a>> wrote:<br>
>> > I performed Ovirt 4.2 upgrade on a 3 host cluster with NFS shared<br>
>> > storage.<br>
>> > The shared storage is mounted from one of the hosts.<br>
>> ><br>
>> > I upgraded the hosted engine first, downloading the 4.2 rpm, doing a yum<br>
>> > update then engine setup which seemed to complete successfully, at the<br>
>> > end<br>
>> > it powered down the hosted VM but it never came back up. I was unable<br>
>> > to<br>
>> > start it.<br>
>> ><br>
>> > I proceeded to upgrade the three hosts, ovirt 4.2 rpm and a full yum<br>
>> > update.<br>
>> > I also rebooted each of the three hosts.<br>
>> ><br>
>> > After some time the hosts did come back and almost all of the VMs are<br>
>> > running again and seem to be working ok with the exception of two:<br>
>> ><br>
>> > 1. The hosted VM still will not start, I've tried everything I can think<br>
>> > of.<br>
>> ><br>
>> > 2. A VM that I know existed is not running and does not appear to exist,<br>
>> > I<br>
>> > have no idea where it is or how to start it.<br>
>> ><br>
>> > 1. Hosted engine<br>
>> ><br>
>> > From one of the hosts I get a weird error trying to start it:<br>
>> ><br>
>> > # hosted-engine --vm-start<br>
>> > Command VM.getStats with args {'vmID':<br>
>> > '4013c829-c9d7-4b72-90d5-6fe58<wbr>137504c'} failed:<br>
>> > (code=1, message=Virtual machine does not exist: {'vmId':<br>
>> > u'4013c829-c9d7-4b72-90d5-6fe5<wbr>8137504c'})<br>
>> ><br>
>> > From the two other hosts I do not get the same error as above, sometimes<br>
>> > it<br>
>> > appears to start but --vm-status shows errors such as: Engine status<br>
>> > : {"reason": "failed liveliness check", "health": "bad", "vm": "up",<br>
>> > "detail": "Up"}<br>
>> ><br>
>> > Seeing these errors in syslog:<br>
>> ><br>
>> > Jan 11 01:06:30 host0 libvirtd: 2018-01-11 05:06:30.473+0000: 1910:<br>
>> > error :<br>
>> > qemuOpenFileAs:3183 : Failed to open file<br>
>> ><br>
>> > '/var/run/vdsm/storage/248f46f<wbr>0-d793-4581-9810-c9d965e2f286/<wbr>c2dde892-f978-4dfc-a421-<wbr>c8e04cf387f9/23aa0a66-fa6c-<wbr>4967-a1e5-fbe47c0cd705':<br>
>> > No such file or directory<br>
>> ><br>
>> > Jan 11 01:06:30 host0 libvirtd: 2018-01-11 05:06:30.473+0000: 1910:<br>
>> > error :<br>
>> > qemuDomainStorageOpenStat:1149<wbr>2 : cannot stat file<br>
>> ><br>
>> > '/var/run/vdsm/storage/248f46f<wbr>0-d793-4581-9810-c9d965e2f286/<wbr>c2dde892-f978-4dfc-a421-<wbr>c8e04cf387f9/23aa0a66-fa6c-<wbr>4967-a1e5-fbe47c0cd705':<br>
>> > Bad file descriptor<br>
>> ><br>
>> > 2. Missing VM. virsh -r list on each host does not show the VM at all.<br>
>> > I<br>
>> > know it existed and is important. The log on one of the hosts even<br>
>> > shows<br>
>> > that it started it recently then stopped in 10 or so minutes later:<br>
>> ><br>
>> > Jan 10 18:47:17 host3 systemd-machined: New machine qemu-9-Berna.<br>
>> > Jan 10 18:47:17 host3 systemd: Started Virtual Machine qemu-9-Berna.<br>
>> > Jan 10 18:47:17 host3 systemd: Starting Virtual Machine qemu-9-Berna.<br>
>> > Jan 10 18:54:45 host3 systemd-machined: Machine qemu-9-Berna terminated.<br>
>> ><br>
>> > How can I find out the status of the "Berna" VM and get it running<br>
>> > again?<br>
>> ><br>
>> > Thanks so much!<br>
>> ><br>
>> > ______________________________<wbr>_________________<br>
>> > Users mailing list<br>
>> > <a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br>
>> > <a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman<wbr>/listinfo/users</a><br>
>> ><br>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>