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:

/etc/os-release became a symlink since https://bugzilla.redhat.com/show_bug.cgi?id=1766754

An issue reported in the original Bugzilla ticket has not been fixed:

https://bugzilla.redhat.com/show_bug.cgi?id=1766754#c16

> # ls -l /usr/lib/os-release /etc/os-release 
> lrwxrwxrwx. 1 root root  22 Mar  9 15:03 /etc/os-release -> ..//usr/lib/os-release
> -rw-r--r--. 1 root root 513 Mar  9 15:03 /usr/lib/os-release
> 
> Is it deliberate that there are // at the beginning of the referenced path in the symlink?
>
> No.  At the same time, it doesn't functionally change anything.  We can fix it in 8.3.0.

Version-Release number of selected component (if applicable):
$ rpm -qa | grep redhat-release
redhat-release-8.6-0.1.el8.x86_64

Let's fix this in RHEL 8.8 and confirm it is already fixed in RHEL 9.

The same issue is found in RHEL9.1

$ cat /etc/os-release
NAME="Red Hat Enterprise Linux"
VERSION="9.1 (Plow)"
ID="rhel"
ID_LIKE="fedora"
VERSION_ID="9.1"
PLATFORM_ID="platform:el9"
PRETTY_NAME="Red Hat Enterprise Linux 9.1 (Plow)"
ANSI_COLOR="0;31"
LOGO="fedora-logo-icon"
CPE_NAME="cpe:/o:redhat:enterprise_linux:9::baseos"
HOME_URL="https://www.redhat.com/"
DOCUMENTATION_URL="https://access.redhat.com/documentation/red_hat_enterprise_linux/9/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"

REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 9"
REDHAT_BUGZILLA_PRODUCT_VERSION=9.1
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="9.1"

$ ls -al /etc/os-release 
lrwxrwxrwx. 1 root root 22 Sep 28 04:07 /etc/os-release -> ..//usr/lib/os-release

$ rpm -qa | grep redhat-release
redhat-release-9.1-1.9.el9.x86_64

Build created: redhat-release-8.8-0.5.el8

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 (redhat-release bug fix and enhancement update), 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-2023:2946