Bug 600118 - need patch backport to rhel for sos integration
Summary: need patch backport to rhel for sos integration
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: corosync
Version: 6.0
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Angus Salkeld
QA Contact: Cluster QE
: 604301 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2010-06-04 00:52 UTC by Steven Dake
Modified: 2016-04-26 15:05 UTC (History)
2 users (show)

Fixed In Version: corosync-1.2.3-3.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-11-15 13:53:22 UTC

Attachments (Terms of Use)
patch ported from trunk (4.03 KB, patch)
2010-06-04 02:55 UTC, Angus Salkeld
no flags Details | Diff

Description Steven Dake 2010-06-04 00:52:54 UTC
Description of problem:
sosreport doesn't capture full intended data

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

How reproducible:

Steps to Reproduce:
1. run sosreport
2. wrong fplay data stored in sosreport
3. corosync-fplay will show the fdata is empty with 0 records
Actual results:
corosync doesn't write flight data on sosreport request

Expected results:
corosync should write flight data on sosreport request

Additional info:

Comment 2 RHEL Product and Program Management 2010-06-04 02:03:15 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for

Comment 3 Angus Salkeld 2010-06-04 02:55:24 UTC
Created attachment 421103 [details]
patch ported from trunk

man page added to another bug (https://bugzilla.redhat.com/show_bug.cgi?id=596550).

Comment 4 Steven Dake 2010-06-21 17:25:43 UTC
*** Bug 604301 has been marked as a duplicate of this bug. ***

Comment 6 releng-rhel@redhat.com 2010-11-15 13:53:22 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.

Note You need to log in before you can comment on or make changes to this bug.