Created attachment 595748 [details] screen shot Description of problem: I blocked master domain from my spm and the host became non-operational the error we are presenting in Task manager is: Handling non responsive Host orange-vdsd and when we expand we only see: Validating 1. this is not a host which is non-responsive, its non-operational which are completely different things caused by different reasons. 2. we offer no information to the user. what does validating mean? Version-Release number of selected component (if applicable): si8 How reproducible: 100% Steps to Reproduce: 1. in two host cluster, block connectivity to master storage domain from spm host 2. 3. Actual results: we see error in Task manager: Handling non responsive Host orange-vdsd Expected results: 1. non-responsive is network issue or communication between rhev to vdsm - this is not a correct alert for storage issue since engine is communicating with the host. 2. when we expand the task all we see is step: validating. please add some more steps - validating is not enough info. if you look at the even log we can see all the different actions run by the system with better explanation than the task manager. Additional info: screen shot
You have attached only a screenshot please attache engine & vdsm log
Created attachment 599977 [details] logs I reproduce it on si11. Attaching engine and vdsm log.
We had asked advice from Omer how to skip the non-responding state in this case. Here is his answer: START ------ i cannot go immediately to non operational, because when you block connection to master from spm, vdsm does service restart to itself == vdsm not responding only when it comes up rhevm can tell that it cannot connect to the storage, and then moved to non operational. what i think should be shown is: 1. handling non responsive host 2. handling non operational host END ---- So, what I understand from the above is that this is not a bug. Please approve
no... this is a bug which is blocked by a vdsm bug (sanlock is restarting the host). once the vdsm bug is fixed you will be able to reproduce this issue.
(In reply to comment #4) > no... this is a bug which is blocked by a vdsm bug (sanlock is restarting > the host). once the vdsm bug is fixed you will be able to reproduce this > issue. So, please privide the vdsm bug on the "depends on" field
information was provided. removing need info
Dafna, I fail to understand the dependency (why this BZ is blocking on BZ#842635 Can you please elaborate ?
Steps to Reproduce: 1. in two host cluster, block connectivity to master storage domain from spm host when you do that the spm reboots = host becomes non-responsive we want to check that the steps of host becoming non-operational are reported in the task manager.
After discussing this issue with Dafna, It looks like this was already handled. Moving to ON_QA for verification