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
wrote:
On Sat, Feb 9, 2019 at 8:58 PM wrote:
I just upgraded an ovirt cluster (hosts and engine) from oVirt 4.2
to 4.3. After I finished
> 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
On Sat, Feb 9, 2019 at 8:58 PM 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
3 matches
Mail list logo
