Description of problem: 1) connect host to storage pool 2) might get the following error message: Thread-78::ERROR::2012-11-20 22:26:32,819::task::853::TaskManager.Task::(_setError) Task=`bcbf77f1-1382-4483-96f9-4390624f31ad`::Unexpected error Traceback (most recent call last): File "/usr/share/vdsm/storage/task.py", line 861, in _run return fn(*args, **kargs) File "/usr/share/vdsm/logUtils.py", line 38, in wrapper res = f(*args, **kwargs) File "/usr/share/vdsm/storage/hsm.py", line 862, in connectStoragePool return self._connectStoragePool(spUUID, hostID, scsiKey, msdUUID, masterVersion, options) File "/usr/share/vdsm/storage/hsm.py", line 904, in _connectStoragePool res = pool.connect(hostID, scsiKey, msdUUID, masterVersion) File "/usr/share/vdsm/storage/sp.py", line 648, in connect self.__rebuild(msdUUID=msdUUID, masterVersion=masterVersion) File "/usr/share/vdsm/storage/sp.py", line 1178, in __rebuild self.masterDomain = self.getMasterDomain(msdUUID=msdUUID, masterVersion=masterVersion) File "/usr/share/vdsm/storage/sp.py", line 1526, in getMasterDomain raise se.StoragePoolWrongMaster(self.spUUID, msdUUID) StoragePoolWrongMaster: Wrong Master domain or its version: 'SD=25a0b810-c6a9-48cc-9f11-9ed816c7648a, pool=96d1b5db-4798-4284-b355-822980dc120d' Thread-78::DEBUG::2012-11-20 22:26:32,822::task::872::TaskManager.Task::(_run) Task=`bcbf77f1-1382-4483-96f9-4390624f31ad`::Task._run: bcbf77f1-1382-4483-96f9-4390624f31ad ('96d1b5db-4798-4284-b355-822980dc120d', 1, '96d1b5db-4798-4284-b355-822980dc120d', '25a0b810-c6a9-48cc-9f11-9ed816c7648a', 1) {} failed - stopping task Thread-78::DEBUG::2012-11-20 22:26:32,822::task::1199::TaskManager.Task::(stop) Task=`bcbf77f1-1382-4483-96f9-4390624f31ad`::stopping in state preparing (force False) expected results: 1) please distinguish between wrong master passed or wrong master version and prompt error accordingly.
Created attachment 649272 [details] vdsm log
I suggest to close this bug, its not really intersting.
Based on Haim comment, and also since the pool is about to be removed in 3.4, closing this bug.