Comment 3Simone Tiraboschi
2018-03-07 08:18:27 UTC
The issue is here:
"status": "non_responsive"
The host went up, then after some time the engine VM lost network communication with the host that has been marked as non_responsive.
The host is still able to start connection to the engine VM and check its status.
It's exactly a duplicate of
https://bugzilla.redhat.com/show_bug.cgi?id=1549642
That can lead to different results according to when engine-host communication got broken.
*** This bug has been marked as a duplicate of bug 1549642 ***