Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1055584 - Rebase corosync to newest upstream version from flatiron branch
Summary: Rebase corosync to newest upstream version from flatiron branch
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: corosync
Version: 6.5
Hardware: All
OS: All
Target Milestone: rc
: ---
Assignee: Jan Friesse
QA Contact: Cluster QE
Depends On:
Blocks: 1056252 1001210 1011307 1018232 1025321 1067043
TreeView+ depends on / blocked
Reported: 2014-01-20 15:08 UTC by Jan Friesse
Modified: 2014-10-14 07:11 UTC (History)
5 users (show)

Fixed In Version: corosync-1.4.7-1.el6
Doc Type: Rebase: Bug Fixes Only
Doc Text:
Rebase package(s) to version: 1.4.7 Highlights and important bug fixes: Release is only about squeeze patch queue. Every important patch was already included or will be included with bug 1001210, bug 1011307, bug 1018232, bug 1025321, bug 1067043 and bug 1005179
Clone Of:
Last Closed: 2014-10-14 07:11:47 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:1508 normal SHIPPED_LIVE corosync bug fix update 2014-10-14 01:22:31 UTC

Description Jan Friesse 2014-01-20 15:08:10 UTC
Description of problem:
Even the corosync in RHEL 6 is 99.9% same as newest upstream release (flatiron branch), it would be nice to rebase for reduce patch queue.

Comment 10 errata-xmlrpc 2014-10-14 07:11:47 UTC
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.

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