In fact, it looks like ovirt thinks its still in maint mode I am presuming because I used the same host name?
--== Host 1 status ==--
Status up-to-date : True
Hostname : node03
Host ID : 1
Engine status : {"reason": "vm not running on this host", "health": "bad", "vm": "down", "detail": "unknown"}
Score : 3400
stopped : False
Local maintenance : False
crc32 : 87e08365
Host timestamp : 3270683
Extra metadata (valid at timestamp):
metadata_parse_version=1
metadata_feature_version=1
timestamp=3270683 (Tue Nov 29 08:43:52 2016)
host-id=1
score=3400
maintenance=False
state=EngineDown
stopped=False
--== Host 2 status ==--
Status up-to-date : True
Hostname : node01
Host ID : 2
Engine status : {"health": "good", "vm": "up", "detail": "up"}
Score : 3400
stopped : False
Local maintenance : False
crc32 : 66c7154a
Host timestamp : 3267326
Extra metadata (valid at timestamp):
metadata_parse_version=1
metadata_feature_version=1
timestamp=3267326 (Tue Nov 29 08:43:44 2016)
host-id=2
score=3400
maintenance=False
state=EngineUp
stopped=False
--== Host 3 status ==--
Status up-to-date : False
Hostname : node02
Host ID : 3
Engine status : unknown stale-data
Score : 0
stopped : False
Local maintenance : True
crc32 : 040b4192
Host timestamp : 211984
Extra metadata (valid at timestamp):
metadata_parse_version=1
metadata_feature_version=1
timestamp=211984 (Mon Nov 28 20:28:06 2016)
host-id=3
score=0
maintenance=True
state=LocalMaintenance
stopped=False
--== Host 4 status ==--
Status up-to-date : True
Hostname : node02
Host ID : 4
Engine status : {"reason": "vm not running on this host", "health": "bad", "vm": "down", "detail": "unknown"}
Score : 0
stopped : False
Local maintenance : True
crc32 : 6aa7d568
Host timestamp : 43683
Extra metadata (valid at timestamp):
metadata_parse_version=1
metadata_feature_version=1
timestamp=43683 (Tue Nov 29 08:44:11 2016)
host-id=4
score=0
maintenance=True
state=LocalMaintenance
stopped=False
In web UI it does not show the node (node02 / Host ID #4) as being in maint. mode