Krutika Dhananjay wrote:
Yes, so the bug has been fixed upstream and the backports to
release-7
and release-8 of gluster pending merge. The fix should be available in
the next .x release of gluster-7 and 8. Until then like Nir suggested,
please turn off performance.stat-prefetch on your volumes.
It looks like I ran exactly into this bug when I wrote this:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/3BQMCIGCEOL...
During my tests, the deployment went through when trying for the third
time - only to discover of course that the problem persists and it, sure
enough came back to haunt me when I rebooted the hosted engine.
I'm not entirely sure I fully understand the problem. What I did, of
course, was this:
# gluster volume set engine performance.stat-prefetch off
It doesn't help with my currently deployed HE - it gets stuck at the
graphical BIOS screen which I can interact with using "hosted-engine
--console" but the best outcome there is to "Reset" which turns the
whole VM off.
Assuming something got lost with the stat-prefetch setting turned on
before: Is there any way to fix this? Will a redeployment surely fix it?
Bonus question: I'm using oVirt Node for the VM and Gluster hosts. Will
a fix be coming by way of package updates for this in the foreseeable
future?
Thank you
Oliver