Hide Forgot
Description of problem: When the host is moved to maintenance by stopping glusterd services and activated back i see that it goes to non operational state saying it fails to attach to hosted_storage domain and engine log reads "ERROR:hosted_storage was reported with error code 358" Version-Release number of selected component (if applicable): ovirt-engine-4.0.5.5-0.1.el7ev.noarch How reproducible: Hit it once. Steps to Reproduce: 1. Move the host to maintenance by stopping glusterd services on the node 2. Update glusterfs and activate it back 3. Actual results: I see that host moves to non operational state saying it fails to attach to one of the storage domain and engine log reads "ERROR : hosted_storage was reported with error code 358" Expected results: There should be smooth transition from maintenance to UP state. Additional info:
Info from engine logs where this error is seen: ================================================== https://paste.fedoraproject.org/492702/42172214/
sosreports can be found in the link below: ================================================= http://rhsqe-repo.lab.eng.blr.redhat.com/sosreports/HC/1400078/
Is this seen with 4.1 as well?
Make sure you put hosted engine to maintenance first - see https://bugzilla.redhat.com/show_bug.cgi?id=1406612#c7 for details.
Moved a host with vms running on it to maintenance by stopping glusterd service on it. Once the node is moved to maintenance, activated it back. I see that node got activated back with out any issues. will reopen this bug if i happen to see it again. version tested : Red Hat Virtualization Manager Version: 4.1.0.3-0.1.el7
Closing based on comment 5