Bug 1031634

Summary:	engine: AutoRecovery of host fails and host is set as NonOperational when export domain continues to be reported with error code 358
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	rhev-integ
Component:	ovirt-engine	Assignee:	Liron Aravot <laravot>
Status:	CLOSED ERRATA	QA Contact:	Aharon Canan <acanan>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.2.0	CC:	abaron, acanan, acathrow, akotov, amureini, anande, bazulay, cboyle, dgibson, hateya, iheim, jkt, laravot, lpeer, lyarwood, Rhev-m-bugs, scohen, tnisan, yeylon
Target Milestone:	---	Keywords:	ZStream
Target Release:	3.2.5
Hardware:	x86_64
OS:	Linux
Whiteboard:	storage
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Prior to this fix, when the host reported the iso/export domain as problematic during the InitVdsOnUp flow, it didn't move to status UP. As currently when ISO/Export domains are reported as problematic by some of the hosts those hosts remain UP and doesn't move to NonOperational, the behaviour between these two flows should be unified - therefore it was decided that when hosts reports iso/export domain as a problem, it won't stop it from moving to UP.	Story Points:	---
Clone Of:	967604	Environment:
Last Closed:	2013-12-18 14:10:44 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Storage	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	967604
Bug Blocks:	1022352

Comment 3 Charlie 2013-11-28 00:42:23 UTC

This bug is currently attached to errata RHBA-2013:16431. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to 
minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:

https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes 

Thanks in advance.

Comment 4 Aharon Canan 2013-12-02 15:49:43 UTC

verified using sf22

simple way to verify/reproduce - 

1. ISCSI DC with one host, data and export domains
2. block the export domain only from your second host before adding it to your setup
3. add the second host to the setup

host should be up, please be aware that no warning appears to the user that the export is not reachable

Comment 5 Sergey Gotliv 2013-12-11 15:16:26 UTC

*** Bug 1032598 has been marked as a duplicate of this bug. ***

Comment 7 errata-xmlrpc 2013-12-18 14:10:44 UTC

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.

http://rhn.redhat.com/errata/RHBA-2013-1831.html