Bug 1400078

Summary: when host is activated from maintenance it goes to non operational state because it cannot attach to hosted_storage
Product: [oVirt] ovirt-engine Reporter: RamaKasturi <knarra>
Component: BLL.HostedEngineAssignee: Doron Fediuck <dfediuck>
Status: CLOSED NOTABUG QA Contact: meital avital <mavital>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.1.0CC: bugs, knarra, sabose
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-03-19 08:30:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Gluster RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description RamaKasturi 2016-11-30 12:21:22 UTC 
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:
Comment 1 RamaKasturi 2016-11-30 12:22:09 UTC 
Info from engine logs where this error is seen:
==================================================
https://paste.fedoraproject.org/492702/42172214/
Comment 2 RamaKasturi 2016-11-30 12:40:23 UTC 
sosreports can be found in the link below:
=================================================
http://rhsqe-repo.lab.eng.blr.redhat.com/sosreports/HC/1400078/
Comment 3 Sahina Bose 2017-01-23 09:44:04 UTC 
Is this seen with 4.1 as well?
Comment 4 Martin Sivák 2017-02-13 10:45:49 UTC 
Make sure you put hosted engine to maintenance first - see https://bugzilla.redhat.com/show_bug.cgi?id=1406612#c7 for details.
Comment 5 RamaKasturi 2017-03-16 07:42:55 UTC 
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
Comment 6 Doron Fediuck 2017-03-19 08:30:46 UTC 
Closing based on comment 5