[ovirt-users] host status "Non Operational" - how to diagnose & fix?
Will Dennis
wdennis at nec-labs.com
Wed Jan 6 02:15:52 UTC 2016
Feel like I’m in a bit of an echo chamber here… Is anyone out there? ;) Or have I worn out the oVirt crew?
Anyhow, not sure if this is a cause, or an effect, but I noticed tonight that the data storage domain (which I’m using Gluster for in a hyperconverged way) is not mounted on the problem hypervisor host…
$ ansible istgroup-ovirt -f 1 -i prod -u root -m shell -a "df -h | grep ':’"
ovirt-node-01 | success | rc=0 >>
localhost:/engine 1.9T 3.0G 1.9T 1% /rhev/data-center/mnt/glusterSD/localhost:_engine
ovirt-node-01.nec-labs.com<http://ovirt-node-01.nec-labs.com>:/vmdata 3.7T 70M 3.7T 1% /rhev/data-center/mnt/glusterSD/ovirt-node-01.nec-labs.com<http://ovirt-node-01.nec-labs.com>:_vmdata
ovirt-node-02 | success | rc=0 >>
localhost:/engine 1.9T 3.0G 1.9T 1% /rhev/data-center/mnt/glusterSD/localhost:_engine
ovirt-node-03 | success | rc=0 >>
localhost:/engine 1.9T 3.0G 1.9T 1% /rhev/data-center/mnt/glusterSD/localhost:_engine
ovirt-node-01.nec-labs.com<http://ovirt-node-01.nec-labs.com>:/vmdata 3.7T 70M 3.7T 1% /rhev/data-center/mnt/glusterSD/ovirt-node-01.nec-labs.com<http://ovirt-node-01.nec-labs.com>:_vmdata
What causes this mount to occur, and is there a way to trigger the mount manually?
On Jan 4, 2016, at 10:47 PM, Will Dennis <wdennis at nec-labs.com<mailto:wdennis at nec-labs.com>> wrote:
I must admit I’m getting a bit weary of fighting oVirt problems at this point… Before I move on to deploying any VMs onto my new infra, I’d like to get the base infra working…
I’m still experiencing a “Non Operational” problem on my “ovirt-node-02” host:
http://s1096.photobucket.com/user/willdennis/media/ovirt-node-02_problem.png.html
More information about the Users
mailing list