Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

I agree this should be done for rhel-7.0.z, too.

I notice that I had filed a bug 1079056 for 7.0(.z) previously already - but it never got approval flags from devel/qa ... only from PM, which indicates that PM would like to see this rebase for 7.0.z.

What should we do? Clone this one for z-stream and close the older bug? Or work with bug 1079056 for z-stream?

(In reply to Kai Engert (:kaie) from comment #3)
> I notice that I had filed a bug 1079056 for 7.0(.z) previously already - but
> it never got approval flags from devel/qa ... only from PM, which indicates
> that PM would like to see this rebase for 7.0.z.
> 
> What should we do? Clone this one for z-stream and close the older bug? Or
> work with bug 1079056 for z-stream?

Since this one is already in modified and has all it's acks, let's close 1079056 as a DUP of this one, and I will ask PM to approve this for zstream.

*** Bug 1079056 has been marked as a duplicate of this bug. ***

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://rhn.redhat.com/errata/RHBA-2015-0472.html