Red Hat Bugzilla – Bug 849907
[engine] ReconstructMasterDomain fails when master domain is unblocked
Last modified: 2016-02-10 15:23:26 EST
Created attachment 605877 [details]
engine + vdsm logs
Description of problem:
After the master domain is blocked (using IPtables) and then unblocked, ReconstructMasterDomain fails repeatedly. Only manually activating the domain resolves the problem
Version-Release number of selected component (if applicable):
Steps to Reproduce:
using automated test with the following scenario:
1. One host, 1 iscsi data domain, 1 ISO domain
2. Block connection from host to data domain
3. unblock connection from host to data domain
domain does not become active again until ActivateDataDomain is manually sent
Domain should reactivate when connection is unblocked
HandleFailedStorageDomainCommand calls ReconstructMasterDomainCommand which calls ConnectStoragePool and RefreshStoragePool, which should fail if the storage server isn't connected.
Manual activation calls (eventually) ConnectStorageServer (in org.ovirt.engine.core.bll.storage.ISCSIStorageHelper.RunConnectionStorageToDomain(storage_domains, Guid, int, LUNs, Guid)), and thus succeeds.
Since there currectly is no connection management in VDSM, I'm guessing the best solution is the to have ConnectStoragePool also imply a call to ConnectStorageServer.
If the server is already connected, VDSM will just silently ignore it.
added Liron as QA contact instead of assignee by mistake.
Ran the automated scenario on SI17 - does not reproduce the problem