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.
Bug 1850463 - RHEL Atomic Host One Month Retirement Notice
Summary: RHEL Atomic Host One Month Retirement Notice
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: rhel-server-atomic
Version: 7.8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Djordje Todorovic
QA Contact: Micah Abbott
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-24 11:29 UTC by Oneata Mircea Teodor
Modified: 2020-07-07 13:07 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-07 13:07:53 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
RHEL Atomic One Month Retirement Notice - 7_6_20 (37.41 KB, application/pdf)
2020-06-24 14:07 UTC, Oneata Mircea Teodor
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:2855 0 None None None 2020-07-07 13:07:56 UTC

Description Oneata Mircea Teodor 2020-06-24 11:29:02 UTC
1 month notice

RHEL Atomic Host Retirement Notice

Description of problem:
Red Hat Enterprise Linux Atomic Host Retirement Notice

Red Hat Enterprise Atomic Host reaches end of life 8/6/20. This retirement notice needs to go out by 7th of July 2020

This is one month retirement notification. 

I also need the package owner to create the errata and publish it by 7th July 2020

Comment 2 Oneata Mircea Teodor 2020-06-24 14:07:07 UTC
Created attachment 1698603 [details]
RHEL Atomic One Month Retirement Notice - 7_6_20

Comment 6 Micah Abbott 2020-07-01 13:10:47 UTC
Verified with redhat-release-atomic-host-7.8-20200504.0.atomic.el7.1.x86_64.rpm

```
$ rpm2cpio redhat-release-atomic-host-7.8-20200504.0.atomic.el7.1.x86_64.rpm | cpio -idmv
./etc/cockpit
./etc/cockpit/ws-certs.d
./etc/issue
./etc/issue.net
./etc/os-release
./etc/pki/product/271.pem
./etc/pki/product/69.pem
./etc/pki/rpm-gpg
./etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-beta
./etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-legacy-former
./etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-legacy-release
./etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-legacy-rhx
./etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
./etc/redhat-release
./etc/rpm/macros.dist
./etc/system-release
./etc/system-release-cpe
./etc/systemd/system/brandbot.path
./usr/lib/os-release
./usr/lib/redhat-release
./usr/lib/sysctl.d/49-coredump.conf
./usr/lib/system-release-cpe
./usr/lib/systemd/system-preset/85-display-manager.preset
./usr/lib/systemd/system-preset/90-default.preset
./usr/share/doc/redhat-release-atomic-host-7.8
./usr/share/doc/redhat-release-atomic-host-7.8/RETIREMENT-NOTICE.txt
./usr/share/doc/redhat-release/GPL
./usr/share/ostree/trusted.gpg.d/RPM-GPG-KEY-redhat-beta.gpg
./usr/share/ostree/trusted.gpg.d/RPM-GPG-KEY-redhat-legacy-former.gpg
./usr/share/ostree/trusted.gpg.d/RPM-GPG-KEY-redhat-legacy-release.gpg
./usr/share/ostree/trusted.gpg.d/RPM-GPG-KEY-redhat-legacy-rhx.gpg
./usr/share/ostree/trusted.gpg.d/RPM-GPG-KEY-redhat-release.gpg
./usr/share/redhat-release/EULA
114 blocks

$ cat ./usr/share/doc/redhat-release-atomic-host-7.8/RETIREMENT-NOTICE.txt
This is the one month notification for the retirement of Red Hat Enterprise
Linux Atomic Host.  This notification applies to customers using Red Hat
Enterprise Linux Atomic Host as part of their Red Hat Enterprise Linux 7
subscription.

Red Hat Enterprise Linux Atomic Host will be retired on August 6, 2020 and
active support will no longer be provided. Accordingly, Red Hat will no longer
provide image or ostree updates, Critical or Important security patches, or
Urgent Priority bug fixes for Red Hat Enterprise Linux Atomic Host after August
6, 2020.

We encourage customers to migrate to the most recent version of Red Hat
Enterprise Linux that is supported for their environment. As a benefit of the
Red Hat subscription model, customers can use their active subscriptions to
entitle any system on any currently supported Red Hat Enterprise Linux release.
Customers who wish to deploy containers as part of their production are
encouraged to evaluate Red Hat OpenShift Container Platform or migrate to a
supported version of Red Hat Enterprise Linux.
```

Comment 8 errata-xmlrpc 2020-07-07 13:07:53 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-2020:2855


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