Re: [ovirt-users] non-operational host issues following 4.2 upgrade

I was able to get my hosts active. During the upgrade, by master data domain's metadata was corrupted -- I had duplicates of some of the dom_md files, and my metadata file was corrupt. Vdsm was looking at that metadata file and throwing up its hands. I added a new data domain but it couldn't take

Re: [ovirt-users] non-operational host issues following 4.2 upgrade

On Wed, Dec 20, 2017 at 11:47 PM, Sandro Bonazzola wrote: > > > 2017-12-21 4:26 GMT+01:00 Jason Brooks : >> >> Hi all, I upgraded my 4 host converged gluster/ovirt lab setup to 4.2 >> yesterday, and now 3 of my hosts won't connect to my main data domain,

Re: [ovirt-users] non-operational host issues following 4.2 upgrade

2017-12-21 4:26 GMT+01:00 Jason Brooks : > Hi all, I upgraded my 4 host converged gluster/ovirt lab setup to 4.2 > yesterday, and now 3 of my hosts won't connect to my main data domain, > so they're non-operational when I try to activate them. > > Here's what seems like a

[ovirt-users] non-operational host issues following 4.2 upgrade

Hi all, I upgraded my 4 host converged gluster/ovirt lab setup to 4.2 yesterday, and now 3 of my hosts won't connect to my main data domain, so they're non-operational when I try to activate them. Here's what seems like a relevant passage of vdsm.log: