Bug 1660645

Summary: Send out RHEL 6.7 EUS Final Retirement Notice
Product: Red Hat Enterprise Linux 6 Reporter: fvarela
Component: redhat-release-serverAssignee: John Francini <jfrancin>
Status: CLOSED ERRATA QA Contact: Jan Blazek <jblazek>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.7CC: fvarela, jfrancin, jreznik, pniahodk, rwilliam, toneata
Target Milestone: rcKeywords: Security
Target Release: ---Flags: fvarela: needinfo+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-01-17 09:21:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
RHEL 6.7 EUS Final Retirement Notice none

Description fvarela 2018-12-18 21:39:09 UTC
Created attachment 1515420 [details]
RHEL 6.7 EUS Final Retirement Notice

Description of problem:
Red Hat Enterprise Linux 6.7 EUS reaches end of life 12/31/2018. The final release notice needs to go out 1/2/19.

This is the fourth retirement notification. 

I also need the package owner to create the errata and publish it.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 John Francini 2018-12-19 20:25:15 UTC
This is going to need rhel-6.7.z and qa_acks granted before it can be turned into an advisory.

Comment 3 John Francini 2018-12-19 20:43:22 UTC
Advisory RHSA-2018:38620 created.

Comment 7 John Francini 2019-01-04 14:38:36 UTC
Sorry. This also should have been moved to MODIFIED, but I missed that step due to the long delay caused by waiting for the 6.7-Z ack.

Comment 14 Pavel Niahodkin 2019-01-15 09:55:39 UTC
Requested information was provided in the above comment.

Comment 17 errata-xmlrpc 2019-01-17 09:21:21 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/RHSA-2019:0095