Description of problem: During execution of gluster peer status if one of the node reboots, gluster peer status fails on that server and during this time node status is shown as non-operational in the UI and general tab logs a message "gluster command failed on server". Once the node is up, status in the UI changes from non-operational to 'UP' but the message in the general tab still remains the same. When the node is UP and running fine, general tab should not show the message "gluster command failed on server" Version-Release number of selected component (if applicable): ovirt-engine-4.0.4.4-0.1.el7ev.noarch How reproducible: Always Steps to Reproduce: 1. Add RHV-H hosts to ovirt-engine 2. Upgrade the nodes from UI 3. Once the upgrade finishes, node reboots Actual results: Once the node is up, in the hosts general tab 'gluster command failed on server' message is seen. Expected results: Since the node is up and the gluster service is running fine, user should not be seeing this message. Additional info:
sosreports can be found at the link http://rhsqe-repo.lab.eng.blr.redhat.com/sosreports/HC/1381175/
If the UI is refreshed, is the message reset on the general tab?
AFAIR, it does not go away with refresh
Is this issue still seen with 4.2? Mughda, can you check?
Can you help clear the needinfo?
This issue is not seen with RHV 4.2.7, and as it not occuring with the latest release, closing this bug