Description of problem:
add an event which would inform about host problem before the host is set to Non Responding. in fact, the host is in Connecting state with red arrow down icon but there's no event for this. it would be nice if any host's status change would be tracked in events.
2014-Nov-24, 12:20
Host ibm-p8-rhevm-02.rhts.eng.brq.redhat.com is non responsive.
2014-Nov-24, 12:18
VM test was started by admin (Host: ibm-p8-rhevm-02.rhts.eng.brq.redhat.com).
2014-Nov-24, 12:12
Host ibm-p8-rhevm-02.rhts.eng.brq.redhat.com power management was verified successfully.
2014-Nov-24, 12:12
Host ibm-p8-rhevm-01.rhts.eng.brq.redhat.com from cluster ppc64-clstr was chosen as a proxy to execute Status command on Host ibm-p8-rhevm-02.rhts.eng.brq.redhat.com.
+++ here it is in state 'Connecting' with red arrow down icon, so i'd like to see an even like:
Host $host from cluster ppc64-clstr is in problematic state, trying to figure
out what's going on...
2014-Nov-24, 12:12
State was set to Up for host ibm-p8-rhevm-02.rhts.eng.brq.redhat.com.
Version-Release number of selected component (if applicable):
3.4.4/av13.2
How reproducible:
100%
Steps to Reproduce:
1. 2 hosts with working PM, block ssh from engine to a host, stop on that host (super)vdsmd
2. observe events in Admin Portal and status on the host
3.
Actual results:
there's no event about host's status change, first event is PM event about status (one could ask himself: why is PM involved?)
Expected results:
add an event about why the host is in Connecting, so one can understand that PM status event is executed because there's something wrong
Additional info:
This was probably resolved indirectly by the PM re-factoring patches that Martin P pushed , setting this to MODIFIED , please test again
(Original patch was abandoned since it seeems irrelevant after Martin patches)
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHEA-2016-0376.html