Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 854295

Summary: [Backend][Storage] Storage domain with corrupted metadata is moved from unknown to active mode and it takes long time untill it's inactivated
Product: Red Hat Enterprise Virtualization Manager Reporter: Jakub Libosvar <jlibosva>
Component: ovirt-engineAssignee: Ayal Baron <abaron>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.1.0CC: amureini, dyasny, gickowic, iheim, lpeer, Rhev-m-bugs, yeylon, ykaul
Target Milestone: ---   
Target Release: 3.1.0   
Hardware: x86_64   
OS: Linux   
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-09-05 15:02:33 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
backend vdsm logs none

Description Jakub Libosvar 2012-09-04 15:05:24 UTC 
Description of problem:
Having two iscsi storage domains and one host I corrupted metadata on master domain. New master was reconstructed correctly but former master was kept in active status instead of inactive.

Version-Release number of selected component (if applicable):
rhevm-backend-3.1.0-14.el6ev.noarch

How reproducible:
Will say later

Steps to Reproduce:
1. Corrupt metadata on master SD
2. Wait till this SD goes down
3.
  
Actual results:
Keeps in active state

Expected results:
Moved to inactive

Additional info:
Backend and vdsm logs from relevant part attached
vdsm log is quite log but the error is repeated, important part is at the beginning
Comment 1 Jakub Libosvar 2012-09-04 15:05:47 UTC 
Created attachment 609716 [details]
backend vdsm logs
Comment 3 Jakub Libosvar 2012-09-05 08:05:31 UTC 
Removing testblocker and decreasing severity - the domain is set to inactive after ~20 minutes (timeout in test was 15 minutes).

The cycle look like this:
Domain is active
Corrupt metadata and trigger failure
Domain is moved to unknown
After 1 minute is moved back to active
After 20 minutes is moved to inactive
Comment 4 Gadi Ickowicz 2012-09-05 15:02:33 UTC 

*** This bug has been marked as a duplicate of bug 853710 ***