Bug 871047

Summary: engine: after iso domain becomes inactive due to connectivity issues -> activating iso domain manually on new spm will re-assign spm
Product: Red Hat Enterprise Virtualization Manager Reporter: Dafna Ron <dron>
Component: ovirt-engineAssignee: Nobody's working on this, feel free to take it <nobody>
Status: CLOSED DUPLICATE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 3.1.0CC: amureini, dyasny, 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-10-29 15:06:09 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
logs none

Description Dafna Ron 2012-10-29 13:43:12 UTC
Created attachment 635017 [details]
logs

Description of problem:

I blocked iso domain from SPM. 
after the storage became inactive I activated a second host and once it became SPM I manually activated the iso domain. 
getFloppyList fails due to permission issue and we re-assign SPM again. 

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

si22.1

How reproducible:

100%

Steps to Reproduce:
1. have one host with iscsi data domain and iso domain which has permission issues. 
2. block connectivity to the iso domain -> storage becomes inactive
3. activate a second host -> new host becomes spm
4. manually activate the iso domain in the new spm  

Actual results:

GetFloppyListVDSCommand fails and engine stops SPM and tries to re-contend the original host - since storage is inaccessible from the original spm we again move SPM back. 

Expected results:

we should not re-contend SPM if getFloppyList or getIsoList fails as long as connectStorageServer succeeded. 

Additional info: logs

Comment 1 Itamar Heim 2012-10-29 15:06:09 UTC

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