Bug 500916
| Summary: | first message of totem stream thrown away - 5.3z stream regression | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Benjamin Kahn <bkahn> |
| Component: | openais | Assignee: | Steven Dake <sdake> |
| Status: | CLOSED ERRATA | QA Contact: | Cluster QE <mspqa-list> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 5.3 | CC: | aconway, cfeist, cluster-maint, cmarthal, edamato, james.leddy, pm-eus, tao |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-06-16 12:58:59 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: | |||
| Bug Depends On: | 497419 | ||
| Bug Blocks: | |||
|
Description
Benjamin Kahn
2009-05-14 20:40:18 UTC
I'm trying out the test case in bz 497419 where you run cpgbench on all nodes, then kill one. It doesn't seem to be working as expected. cpgbench on one node is not receiving any more messages and the killed node is not being let back into the cluster. There is this message in the logs: Jun 12 13:54:24 z5 openais[3413]: [EVT ] Evt config msg from nodeid r(0) ip(10.15.89.15) , but not in membership change I ran the test case again without cman and hit the same message from EVT. When trying to restart cpgbench on the rejoined node I got the message: [root@z5 tmp]# ./cpgbench cpg_join failed with result 6 Which Ryan tells me is TRY_AGAIN which is the error in the original bug report. Moving this back to ASSIGNED. the bug you see is not a regression and has been in the source tree for some time apparently. Please file a new bugzilla. I'll work with you on irc to see if we can come up with some way to verify this bugzilla you are qeing problem is resolved. Regards -steve After further testing and discussions with the developer it was determined that the behavior seen is a different bug, filed as bz 506119, which is not a regression. It was also determined that this bug could not be verified without instrumenting the code. 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-2009-1104.html |