Red Hat Bugzilla – Bug 1011505
AcquireLockFailure failed to AttachStorageDomainVDS, Cannot obtain lock, wrong lease value
Last modified: 2016-06-26 19:50:46 EDT
Description of problem:
When attaching a storage domain (iscsi) to the datacenter vdsm fails and throws the error:
2013-09-24 11:50:17,855 ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.AttachStorageDomainVDSCommand] (ajp-/127.0.0.1:8702-3) Error code AcquireLockFailure and error message IRSGenericException: IRSErrorException: Failed to AttachStorageDomainVDS, error = Cannot obtain lock: "id=df36e06f-9085-4f54-b0ba-edc02af6039a, rc=1, out=, err=['panic:  validate_lease_params: bad lease/op max timeouts: (Success)']"
It seems that the lease parameter has the wrong value.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Create iscsi datacenter
3.Create storage domain
4.Attach storage domain to cluster
You can check the jenkins job here:
Not moving to POST yet as I don't know yet if the patch provided addresses all the issues.
Moving to POST since at least one scenario is covered.
Patch does not address the problem
(In reply to Ayal Baron from comment #3)
> Patch does not address the problem
Please ignore, this is not correct.
Verified on is17.1 - attaching second domain and export domain works as expected
This bug is currently attached to errata RHBA-2013:15291. 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.
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.