Bug 737329

Summary:	Connect storage pool with inaccessible master domain should raise StoragePoolMasterNotFound
Product:	Red Hat Enterprise Linux 6	Reporter:	Igor Lvovsky <ilvovsky>
Component:	vdsm	Assignee:	Eduardo Warszawski <ewarszaw>
Status:	CLOSED ERRATA	QA Contact:	Daniel Paikov <dpaikov>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2	CC:	abaron, bazulay, danken, hateya, iheim, lpeer, ykaul
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	storage
Fixed In Version:	vdsm-4.9-101	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-12-06 07:28:27 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Igor Lvovsky 2011-09-11 07:18:28 UTC

Description of problem:
If during connectStoragePool master domain not found we should return StoragePoolMasterNotFound and not "Domain does not exists"

Version-Release number of selected component (if applicable):


How reproducible:
always on NFS

Steps to Reproduce:
1. connect storage pool with 2 data domains on different storage servers
2. block master domain with iptables 
3. 
  
Actual results:
1. vdsm will restart itself.
2. RHEV-M will try connectStoragePool with inaccessible master
3. vdsm return "domain does not exists"
4. RHEV-M will run step 2 several times untill it decide to run reconstructMaster

Expected results:
1. vdsm will restart itself.
2. RHEV-M will try connectStoragePool with inaccessible master
3. vdsm return StoragePoolMasterNotFound 
4. RHEV-M will run reconstructMaster



Additional info:

Comment 1 Dan Kenigsberg 2011-09-11 07:33:03 UTC

http://gerrit.usersys.redhat.com/903

Comment 4 Daniel Paikov 2011-09-21 09:10:41 UTC

Checked on 4.9-104.

Comment 5 errata-xmlrpc 2011-12-06 07:28:27 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/RHEA-2011-1782.html