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:

The paxos code was doing some unnecessary host_id checks when the same
host re-acquired a lease after it was uncleanly shut down previously.

test: existing failure/recovery tests should continue to work the same

commit
sanlock: fix paxos acquire host_id check

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

To test this code path, a host needs to be holding a lease, and then be reset/restarted in some way such that it does not record the lease as free on storage, i.e. the lease on disk still shows that the host holds it, but the host has in fact lost the lease.  Once restarted, the host should be made to acquire the same lease.  At this point it will see that it's still the owner on disk, although with a previous generation.

A couple ways you could cause a host to be restarted without releasing a lease on disk:
- Disconnect the storage holding the lease from the host.
- Reset power on the host while it's holding a lease.

storage disconnected from the host and reconnected after several minutes. the host acquired the same lease that it was holding before. 


sanlock-2.3-4.el6_3.x86_64

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.

http://rhn.redhat.com/errata/RHBA-2012-1507.html