RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

trying to attach an iso domain to pool I got an error: 

AcquireLockFailure: Cannot obtain lock: "id=eebcad17-cbf7-4098-880d-81e2c2504169, rc=1, out=['error - lease file does not exist or is not writeable'

please close this bug as duplicate is this is clone of: 818632

I think that it is a clone since I ran reconstruct master when putting domains in maintenance which is similar to the other scenario. 


Version-Release number of selected component (if applicable):

vdsm-4.9.6-9.el6.x86_64
si3

How reproducible:


Steps to Reproduce:
1. put master domain in maintenance when there are two domain
2. deactivate all domain
3. activate master domain 
4. try to attach an iso domain 
  
Actual results:

we get a cannot obtain lock on iso domain 

Expected results:

we should be able to attach the iso to pool


Additional info: logs

Created attachment 582474 [details]
log

Since RHEL 6.3 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

(In reply to comment #0)
> Description of problem:
> 
> trying to attach an iso domain to pool I got an error: 
> 
> AcquireLockFailure: Cannot obtain lock:
> "id=eebcad17-cbf7-4098-880d-81e2c2504169, rc=1, out=['error - lease file
> does not exist or is not writeable'

Did you check if the lease file was present and if it was accessible?
Could you try to reproduce to see if it was just a problem of that specific iso domain?

Two months passed and we didn't hear any other report on this. The current vdsm version is vdsm-4.9.6-23.0.el6_3. Feel free to reopen (but make sure that you are reproducing with safelease).