Bug 786735
| Summary: | totem: Correct nodeid of token when we retransmit it | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Jan Friesse <jfriesse> | ||||
| Component: | corosync | Assignee: | Jan Friesse <jfriesse> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Cluster QE <mspqa-list> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 6.2 | CC: | cluster-maint, jkortus, sdake | ||||
| Target Milestone: | rc | ||||||
| Target Release: | 6.3 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | corosync-1.4.1-8.el6 | Doc Type: | Bug Fix | ||||
| Doc Text: |
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.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-02-21 07:49:58 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
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.