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

Bug 1583602

Summary: Storage domain deactivation failed during connectStoragePool on StoragePoolWrongMaster (gluster domain)
Product: [oVirt] vdsm Reporter: Elad <ebenahar>
Component: CoreAssignee: Nobody <nobody>
Status: CLOSED DEFERRED QA Contact: Avihai <aefrat>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.20.23CC: bugs, eshenitz, ngavrilo, tnisan
Target Milestone: ---Keywords: Automation
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-08-24 12:19:42 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 Elad 2018-05-29 10:56:40 UTC
Description of problem:
While a Gluster domain was the master, during connect storage pool I got StoragePoolWrongMaster


Version-Release number of selected component (if applicable):
vdsm-4.20.28-1.el7ev.x86_64
sanlock-3.6.0-1.el7.x86_64
glusterfs-3.8.4-54.8.el7.x86_64


How reproducible:
Happened once

Steps to Reproduce:
1. Deactivate master domain (Gluster)


Actual results:
Storage domain deactivation failed during connect storage pool:

2018-05-27 20:28:22,220+0300 INFO  (jsonrpc/4) [vdsm.api] FINISH connectStoragePool error=Wrong Master domain or its version: 'SD=3db1d26f-0760-43d5-a080-03e2faf446e0, pool=0fcc53f2-bf9c-4d5a-aa22-22539b1077a4' 
from=::ffff:10.35.161.127,55174, flow_id=656c4fb2, task_id=9e212130-e327-4fa2-ba37-cfcb40dd9185 (api:50)
2018-05-27 20:28:22,221+0300 ERROR (jsonrpc/4) [storage.TaskManager.Task] (Task='9e212130-e327-4fa2-ba37-cfcb40dd9185') Unexpected error (task:875)
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 882, in _run
    return fn(*args, **kargs)
  File "<string>", line 2, in connectStoragePool
  File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 48, in method
    ret = func(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 1035, in connectStoragePool
    spUUID, hostID, msdUUID, masterVersion, domainsMap)
  File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 1075, in _connectStoragePool
    masterVersion, domainsMap)
  File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 1055, in _updateStoragePool
    pool.refresh(msdUUID, masterVersion)
  File "/usr/lib/python2.7/site-packages/vdsm/storage/sp.py", line 1353, in refresh
    self.__rebuild(msdUUID=msdUUID, masterVersion=masterVersion)
  File "/usr/lib/python2.7/site-packages/vdsm/storage/sp.py", line 1292, in __rebuild
    raise se.StoragePoolWrongMaster(self.spUUID, msdUUID)
StoragePoolWrongMaster: Wrong Master domain or its version: 'SD=3db1d26f-0760-43d5-a080-03e2faf446e0, pool=0fcc53f2-bf9c-4d5a-aa22-22539b1077a4'
2018-05-27 20:28:22,221+0300 DEBUG (jsonrpc/4) [storage.TaskManager.Task] (Task='9e212130-e327-4fa2-ba37-cfcb40dd9185') Task._run: 9e212130-e327-4fa2-ba37-cfcb40dd9185 ('0fcc53f2-bf9c-4d5a-aa22-22539b1077a4', 2,
 '3db1d26f-0760-43d5-a080-03e2faf446e0', 3, {'2c11243a-6f5a-4ea3-9588-7be52ba1d979': 'active', '1034f6da-f48a-4a36-b077-e7e591ecf5ae': 'active', '42ad4e29-9675-43d2-ab35-bf5e962eef88': 'active', 'be3723d4-5f0c-4
050-8747-7fd4e9822d20': 'active', '66b6247a-c9d1-4d00-9474-398aa892dfd8': 'active', 'd89ad1d4-cce1-4c55-b849-db301eb5eb6a': 'active', '8f14164b-84c1-4e73-9073-024260b61795': 'active', '39b805d8-a068-42cc-be7d-10
ae553c2c00': 'active', 'c0a56311-97f6-4e10-9059-68f7a8ce7db0': 'active', '3db1d26f-0760-43d5-a080-03e2faf446e0': 'attached'}) {} failed - stopping task (task:894)



Expected results:
Storage domain deactivation failed

Additional info:
engine and vdsm logs

Comment 1 Elad 2018-05-29 10:58:30 UTC
Created attachment 1445336 [details]
logs

Comment 2 Sandro Bonazzola 2019-01-28 09:36:50 UTC
This bug has not been marked as blocker for oVirt 4.3.0.
Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.

Comment 3 Eyal Shenitzky 2021-08-24 12:19:42 UTC
This bug/RFE is more than 2 years old and it didn't get enough attention therefore can be closed.
Please re-open if you think it is still relevant.