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.

s/
DIAGNOSTICS
       All  tools return a status code of zero on success or non-zero on fail-
       ure.
/
DIAGNOSTICS
       All  tools return a status code of zero on success or non-zero on fail-
       ure.  Non-zero exit codes may change and should not be assumed to imply
       specific errors.
/

agk, can you look over the proposed change above?  If you are happy with it, let's check it in.  It should prevent other users from assuming exit values mean specific things.

Text extended in 2.02.165

Verified new warning about the dynamic nature of exit codes/messages:


3.10.0-501.el7.x86_64
lvm2-2.02.165-1.el7    BUILT: Wed Sep  7 11:04:22 CDT 2016


DIAGNOSTICS
       All  tools  return a status code of zero on success or non-zero on failure.  The non-zero codes distinguish only between the broad categories of unrecognised commands, problems processing the
       command line arguments and any other failures.  As LVM remains under active development, the code used in a specific case occasionally changes between releases.  Message text may also change.

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.

https://rhn.redhat.com/errata/RHBA-2016-1445.html