Bug 1017177

Summary: [engine] Master domain is not reconstructed when losing connectivitiy to master domain from all hosts in DC
Product: Red Hat Enterprise Virtualization Manager Reporter: Raz Tamir <ratamir>
Component: ovirt-engineAssignee: Liron Aravot <laravot>
Status: CLOSED CURRENTRELEASE QA Contact: Leonid Natapov <lnatapov>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 3.3.0CC: abaron, acathrow, amureini, eedri, iheim, lpeer, Rhev-m-bugs, scohen, yeylon
Target Milestone: ---Flags: amureini: Triaged+
Target Release: 3.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: storage
Fixed In Version: is21 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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:
Bug Depends On:    
Bug Blocks: 1032811    
Attachments:
Description Flags
engine log
none
vdsm log none

Description Raz Tamir 2013-10-09 11:35:30 UTC
Created attachment 809859 [details]
engine log

Description of problem:
When trying to execute some actions (e.g. create snapshot, make template etc.) and blocking connectivity to Master storage domain from all hosts using iptables immediately after the action was executed, the master domain should become inactive and ReconstructMasterDomainCommand should be called.
The master's domain status changes to inactive as expected, but ReconstructMasterDomainCommand does not succeed.


Version-Release number of selected component (if applicable):
rhevm-3.3.0-0.24.master.el6ev.noarch

How reproducible:
100%

Steps to Reproduce:

setup with 1 iSCSI DC, 2 host, 2 storage domain which each on different servers and 1 vm.

1. Perform any action that involves the VM's storage (e.g. remove template, create snapshot, remove vm or disks)

2. Immediately after you run the action , block connectivity to Master storage domain from all hosts using iptables

Actual results:
We should fail the action performed in step 1 gracefully

Expected results:
Stuck in process with no actual result.
from the engine log it is obvious that the engine is in continuous loop, without reconstructing the master domain

Additional info:

Comment 1 Raz Tamir 2013-10-09 12:24:38 UTC
Created attachment 809881 [details]
vdsm log

Comment 3 Leonid Natapov 2013-11-19 09:30:49 UTC
is23. Tested according steps to reprduce.

Comment 4 Itamar Heim 2014-01-21 22:27:55 UTC
Closing - RHEV 3.3 Released

Comment 5 Itamar Heim 2014-01-21 22:27:56 UTC
Closing - RHEV 3.3 Released

Comment 6 Itamar Heim 2014-01-21 22:30:52 UTC
Closing - RHEV 3.3 Released