That ended up being the issue. I manually changed the permissions and
engine started again.
On Sat, Feb 9, 2019 at 1:09 PM, Simone Tiraboschi <stirabos(a)redhat.com>
wrote:
On Sat, Feb 9, 2019 at 8:58 PM <dbrandon.johnson(a)gmail.com> wrote:
> I just upgraded an ovirt cluster (hosts and engine) from oVirt 4.2
> to 4.3. After I finished upgrading the hosts from 4.2 to 4.3 engine
> stopped working and now it will not start. Looking at VDSM it is
> looking for a path that isn't getting mounted by the hosted engine
> when I try to connect storage and start the VM.
> VDSM log:
>
https://paste.fedoraproject.org/paste/aOi4aDMMNmDqpD72SdcI0A
>
> the path that it is mounting at is:
> /rhev/data-center/mnt/glusterSD/hyper2-gluster.storage.open-tec.net:_engine
> and I think it is expecting
> /rhev/data-center/00000000-0000-0000-0000-000000000000
>
> Any help on this would be appreciated.
Can you please check this?
https://bugzilla.redhat.com/1666795
It seems that under certain unclear circumstances, during 4.2 -> 4.3
host upgrade, the file ownership and permissions of VMs disks got set
as root:root and 640 instead of vdsm:kvm and 660 and so vdsm fails to
start the engine VM.
Manually fixing it seems enough to bring the engine again.
Can you please check and report? if it's that, it definitively
deserves more attention since we already got more than one evidence.
> _______________________________________________
> Users mailing list -- users(a)ovirt.org
> To unsubscribe send an email to users-leave(a)ovirt.org
> Privacy Statement:
https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
>
https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
>
https://lists.ovirt.org/archives/list/users@ovirt.org/message/6JFTGJ37KDZ...