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:
If cman_tool join runs corosync and that exit with failure, something like "Error, reason code is 12" is displayed. It should be nice to display something more meaningful like openais in RHEL5 does.

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

How reproducible:
100%

Steps to Reproduce (really example, same is with no memory error, ...):
1. rm -rf /var/lib/corosync
2. cman_tool join
  
Actual results:
corosync died: Error, reason code is 16

Expected results:
corosync died: Error, Required directory not present /var/lib/corosync.  Please create it.

Additional info:
There are other exit codes and none of them is handled correctly.

Main reason is because old aisexec returned negative return codes (or from other side, very big positive numbers ;) ). Current corosync return only (small) positive numbers.

Created attachment 433735 [details]
Proposed patch

Patch handles corosync exit codes.

This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **

Patch is currently included in STABLE3 git tree as 2197cb026309d18b864dd2eb10754b095090db40

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0537.html