Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Cause
Corosync entered recovery state.
Consequence
Incorrect nodeid was sent in recovery messages. This is NOT visible by users, but it may make harder to debug problems in source code (by developers or SEG)
Fix
Set correct nodeid.
Result
Nodeid is correctly set.
Created attachment 559016[details]
Proposed patch from flatiron branch in git
Description of problem:
Although incorrect nodeid will not affect program's logic, but it will
make us confused when we add some logs to record the transmission path of
token in debug mode.
Version-Release number of selected component (if applicable):
flatiron
How reproducible:
100%
Steps to Reproduce:
1. Debug nodeid
Actual results:
Incorrect nodeid
Expected results:
Correct nodeid
Additional info:
This doesn't affect customers. It "can" be helpful for GSS and/or developers. Doesn't need to be QA, so sanity only tests are recommended.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Cause
Corosync entered recovery state.
Consequence
Incorrect nodeid was sent in recovery messages. This is NOT visible by users, but it may make harder to debug problems in source code (by developers or SEG)
Fix
Set correct nodeid.
Result
Nodeid is correctly set.
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-2013-0497.html
Created attachment 559016 [details] Proposed patch from flatiron branch in git Description of problem: Although incorrect nodeid will not affect program's logic, but it will make us confused when we add some logs to record the transmission path of token in debug mode. Version-Release number of selected component (if applicable): flatiron How reproducible: 100% Steps to Reproduce: 1. Debug nodeid Actual results: Incorrect nodeid Expected results: Correct nodeid Additional info: This doesn't affect customers. It "can" be helpful for GSS and/or developers. Doesn't need to be QA, so sanity only tests are recommended.