Red Hat Bugzilla – Bug 879253
3.2 - [vdsm] ConnectStoragePool fail with 2 hosts in NFS due to stale cache
Last modified: 2016-02-10 15:21:15 EST
Created attachment 649788 [details]
vdsm + engine logs
Description of problem:
When creating the first storage domain in a setup 2 hosts, hosts fail to create the initial pool, with an error during connectStoragePool - "Wrong Master Domain or Version" due to stale cache in vdsm.
The following flow is executed:
1. ConnectStorageServer is sent to Host1
2. CreateStorageDomain is sent to Host1
3. CreateStoragePool is sent to Host2 (After connectStorageServer)
4. ConnectStoragePool is sent to Host1 and fails
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Reproduced with automated test that performs the following:
1. Add hosts
2. Create storage domain (NFS)
3. Attach storage domain to datacenter
ConnectStoragePool fails with error described above
ConnectStoragePool should succeed
Isn't it a regression?
(In reply to comment #2)
> Isn't it a regression?
Yes, from SI24.2.
suspicious commit: 9814e4c5745d84b805f5d93cc3a5e979b2fc25e3
Fede, isn't this http://gerrit.ovirt.org/#/c/9422/ ?
If so please update commit message and move to post.
Author: Federico Simoncelli <firstname.lastname@example.org>
Date: Thu Nov 22 09:04:00 2012 -0500
sdcache: add refresh to connectStoragePool
Signed-off-by: Federico Simoncelli <email@example.com>
*** Bug 882641 has been marked as a duplicate of this bug. ***
Verified on SF10. 3 reproductions succeeded.
This bug is currently attached to errata RHBA-2012:14332. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.
Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:
* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')
Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.
For further details on the Cause, Consequence, Fix, Result format please refer to:
Thanks in advance.
Doc Text is correct.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.