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:

When libvirt call sanlock, it includes sanlock error code (e.g. -220) in libvirt
log and in libvirt error messages.

Sanlock added recently new sanlock_strerror api, returning a more useful short
description of the error:

commit c8ce851b260d2a3dd00ebc3f3b0cc4909522b101
Author: David Teigland <teigland>
Date:   Tue Jan 3 13:49:12 2017 -0600

    sanlock: add strerror function
    
    to get a short string description of error numbers.

It would be useful to use the new api to include the error description in addition
to the error code.

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

*** This bug has been marked as a duplicate of bug 1409511 ***