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 1364203 - MRG-M 3.2.2 RHEL-7 errata placeholder
Summary: MRG-M 3.2.2 RHEL-7 errata placeholder
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp
Version: 3.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: 3.2.2
: ---
Assignee: messaging-bugs
QA Contact: Messaging QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-04 17:32 UTC by Mike Cressman
Modified: 2016-10-11 08:56 UTC (History)
3 users (show)

Fixed In Version: qpid-cpp-0.34-17
Doc Type: Release Note
Doc Text:
The RHEL-7 version of the errata will need to get the doc text for the individual bugs from the RHEL-6 version of the errata (where all the bugs are attached).
Clone Of:
Environment:
Last Closed: 2016-10-11 08:56:45 UTC


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2048 normal SHIPPED_LIVE Red Hat Enterprise MRG Messaging 3.2.2 Bug Fix Release 2016-10-11 12:56:23 UTC

Description Mike Cressman 2016-08-04 17:32:03 UTC
Description of problem:

To create a MRG 3.2.2 errata for RHEL-7, we need a BZ.  All the BZ's for this release are the same for both RHEL-6 and RHEL-7, so we put all the bugs in the RHEL-6 errata and use a placeholder for RHEL-7.

Comment 3 errata-xmlrpc 2016-10-11 08:56:45 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.

https://access.redhat.com/errata/RHBA-2016:2048


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