Re: [ovirt-users] unable to bring up hosted engine after botched 4.2 upgrade

Hi, the VM is up according to the status (at least for a while). You should be able to use console and diagnose anything that happened inside (line the need for fsck and such) now. Check the presence of those links again now, the metadata file content is not important, but the file has to exist

Re: [ovirt-users] unable to bring up hosted engine after botched 4.2 upgrade

> Can you please stop all hosted engine tooling ( On all hosts I should have added. Martin On Fri, Jan 12, 2018 at 3:22 PM, Martin Sivak wrote: >> RequestError: failed to read metadata: [Errno 2] No such file or directory: >>

Re: [ovirt-users] unable to bring up hosted engine after botched 4.2 upgrade

> RequestError: failed to read metadata: [Errno 2] No such file or directory: > '/var/run/vdsm/storage/248f46f0-d793-4581-9810-c9d965e2f286/14a20941-1b84-4b82-be8f-ace38d7c037a/8582bdfc-ef54-47af-9f1e-f5b7ec1f1cf8' > > ls -al >

Re: [ovirt-users] unable to bring up hosted engine after botched 4.2 upgrade

The blockIoTune error should be harmless. It is just a result of a data check by other component (mom) that encountered a VM that no longer exists. I thought we squashed all the logs like that though.. Martin On Fri, Jan 12, 2018 at 3:12 PM, Jayme wrote: > One more thing to

Re: [ovirt-users] unable to bring up hosted engine after botched 4.2 upgrade

One more thing to add, I've also been seeing a lot of this in the syslog as well: Jan 12 10:10:49 cultivar2 journal: vdsm jsonrpc.JsonRpcServer ERROR Internal server error#012Traceback (most recent call last):#012 File "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 606, in

Re: [ovirt-users] unable to bring up hosted engine after botched 4.2 upgrade

Thanks for the help thus far. Storage could be related but all other VMs on same storage are running ok. The storage is mounted via NFS from within one of the three hosts, I realize this is not ideal. This was setup by a previous admin more as a proof of concept and VMs were put on there that

Re: [ovirt-users] unable to bring up hosted engine after botched 4.2 upgrade

On Fri, Jan 12, 2018 at 11:11 AM, Martin Sivak wrote: > Hi, > > the hosted engine agent issue might be fixed by restarting > ovirt-ha-broker or updating to newest ovirt-hosted-engine-ha and > -setup. We improved handling of the missing symlink. > Available just in oVirt 4.2.1

[ovirt-users] unable to bring up hosted engine after botched 4.2 upgrade

Please help, I'm really not sure what else to try at this point. Thank you for reading! I'm still working on trying to get my hosted engine running after a botched upgrade to 4.2. Storage is NFS mounted from within one of the hosts. Right now I have 3 centos7 hosts that are fully updated with