Bug 989131 - [vdsm] host is unable to connect to the pool after connectivity issues have been solved
[vdsm] host is unable to connect to the pool after connectivity issues have b...
Status: CLOSED DUPLICATE of bug 986652
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm (Show other bugs)
x86_64 Unspecified
unspecified Severity urgent
: ---
: 3.3.0
Assigned To: Ayal Baron
: Regression, Triaged
Depends On:
  Show dependency treegraph
Reported: 2013-07-27 14:53 EDT by Elad
Modified: 2016-02-10 12:55 EST (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-08-08 03:40:37 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: Storage
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
logs (4.95 MB, application/x-gzip)
2013-07-27 14:53 EDT, Elad
no flags Details

  None (edit)
Description Elad 2013-07-27 14:53:08 EDT
Created attachment 779177 [details]

Description of problem:
Host fails in connectStoragePool after connectivity problems to one of the pool's domains was solved. vdsm is unable to find the pool's master domain:

StoragePoolMasterNotFound: Cannot find master domain: 'spUUID=1def1ef4-b354-424d-9fbe-25e40400db64, msdUUID=b38adea3-3a54-4f65-a7aa-07a17482be00'

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

How reproducible:

Steps to Reproduce:
1. on a block pool with more than 1 host and more than 1 data domain
2. block connectivity between HSM to non-master domain using iptables, engine will set host to 'non-operational'
3. resume connectivity, and activate the host

Actual results:
Host will fail to connect to the pool. Host is unable to find master storage domain:

Thread-41181::ERROR::2013-07-27 20:47:35,006::task::850::TaskManager.Task::(_setError) Task=`48f9660b-c25e-497e-880e-54bef55fbb60`::Unexpected error
Traceback (most recent call last):
  File "/usr/share/vdsm/storage/task.py", line 857, in _run
    return fn(*args, **kargs)
  File "/usr/share/vdsm/logUtils.py", line 45, in wrapper
    res = f(*args, **kwargs)
  File "/usr/share/vdsm/storage/hsm.py", line 991, in connectStoragePool
    masterVersion, options)
  File "/usr/share/vdsm/storage/hsm.py", line 1038, in _connectStoragePool
    res = pool.connect(hostID, scsiKey, msdUUID, masterVersion)
  File "/usr/share/vdsm/storage/sp.py", line 698, in connect
    self.__rebuild(msdUUID=msdUUID, masterVersion=masterVersion)
  File "/usr/share/vdsm/storage/sp.py", line 1235, in __rebuild
  File "/usr/share/vdsm/storage/sp.py", line 1594, in getMasterDomain
    raise se.StoragePoolMasterNotFound(self.spUUID, msdUUID)
StoragePoolMasterNotFound: Cannot find master domain: 'spUUID=1def1ef4-b354-424d-9fbe-25e40400db64, msdUUID=b38adea3-3a54-4f65-a7aa-07a17482be00'

storage pool is not present under /rhev/data-center/ :

[root@green-vdsa data-center]# ll
total 12
drwxr-xr-x. 2 vdsm kvm 4096 Feb  6 16:17 9ca4f342-afd8-4c5f-97ca-0039d5d261d4
drwxr-xr-x. 2 vdsm kvm 4096 Jul 25 10:37 hsm-tasks
drwxr-xr-x. 7 vdsm kvm 4096 Jul 22 16:37 mnt

Expected results:
After connectivity problem to one of the domains was solved, host should be able to connect to the pool

Additional info:
Comment 3 Allon Mureinik 2013-08-08 03:40:37 EDT

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

Note You need to log in before you can comment on or make changes to this bug.