Bug 845824 - [engine-core] auto-recovery: DisconnectStorageServer (umount) is not sent after failed attempt to Activate Storage Domain
Summary: [engine-core] auto-recovery: DisconnectStorageServer (umount) is not sent aft...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 3.1.0
Assignee: Ayal Baron
QA Contact: Haim
URL:
Whiteboard: storage
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-05 11:45 UTC by Gadi Ickowicz
Modified: 2016-02-10 17:17 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-22 14:46:40 UTC
oVirt Team: Storage
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
engine + vdsm logs (1.11 MB, application/x-gzip)
2012-08-05 11:45 UTC, Gadi Ickowicz 		no flags Details
View All

Description Gadi Ickowicz 2012-08-05 11:45:32 UTC 
Created attachment 602353 [details]
engine + vdsm logs

Description of problem:
When AutoRecover fails to recover a storage domain, DisconnectStorageServer is not sent.


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


How reproducible:
100%

Steps to Reproduce:
1. On a cluster with 2 domains, edit metadata of master storage domain to corrput it
2. Reconstruct is done automatically and 2nd domain is set as master
3. every 5 minutes AutoRecover flow runs automatically and should disconnectStorageServer but it doesn't
  
Actual results:
On AutoRecover flow (every 5 minutes) connectStorageServer is sent, and after failure to reconnect to domain due to corrupt metadata, disconnectStorageServer is not sent, and the connection remains active

Expected results:
disconnectStorageServer should be sent to disconnect when failed to connect to a host

Additional info:
Comment 1 Ayal Baron 2012-08-22 14:46:40 UTC 
no it shouldn't.
disconnecting all the time is a bug.
Note You need to log in before you can comment on or make changes to this bug.