Bug 695355

Summary: [vdsm][Storage] repoStats reports inaccessible storage domain as valid.
Product: Red Hat Enterprise Linux 6 Reporter: David Naori <dnaori>
Component: vdsmAssignee: Saggi Mizrahi <smizrahi>
Status: CLOSED ERRATA QA Contact: Daniel Paikov <dpaikov>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.2CC: abaron, bazulay, danken, hateya, iheim, mgoldboi, ykaul
Target Milestone: rcKeywords: Regression, TestBlocker
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: storage
Fixed In Version: vdsm-4.9-61 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 695477 (view as bug list) Environment:
Last Closed: 2011-12-06 07:14:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 695477    
Attachments:
Description Flags
vdsm log none

Description David Naori 2011-04-11 13:28:16 UTC
Created attachment 491234 [details]
vdsm log

Description of problem:
when losing connection to a non-master SD- repoStats dose not report the domain as invalid -If no operation is done on the SD.

Version-Release number of selected component (if applicable):
vdsm-4.9-58.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1.have two SD (block-device)
2.block connection to non-master SD
  
Actual results:
repoStats report the blocked SD as valid.

Expected results:
repoStats should report the domain as invalid

vdsm logs attached.

Comment 2 Dan Kenigsberg 2011-04-17 22:01:55 UTC
http://gerrit.usersys.redhat.com/#change,281

Comment 4 Daniel Paikov 2011-05-01 13:41:43 UTC
Checked on vdsm-4.9-63.

Comment 5 errata-xmlrpc 2011-12-06 07:14:15 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