[ovirt-users] host status "Non Operational" - how to diagnose & fix?
Will Dennis
wdennis at nec-labs.com
Wed Jan 6 14:12:16 UTC 2016
I did what Joop suggested (put -node-02 into maint, clear vdsm.log on -node-02, clear engine.log on HE, then activate -node-02) and — what do you know, the node came up into an operational state! It was able to successfully mount the data SD this time:
$ 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:/vmdata 3.7T 70M 3.7T 1% /rhev/data-center/mnt/glusterSD/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-01.nec-labs.com:/vmdata 3.7T 70M 3.7T 1% /rhev/data-center/mnt/glusterSD/ovirt-node-01.nec-labs.com:_vmdata
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:/vmdata 3.7T 70M 3.7T 1% /rhev/data-center/mnt/glusterSD/ovirt-node-01.nec-labs.com:_vmdata
Wonder what the magic was? ;) I’ll take the result anyways :)
More information about the Users
mailing list