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.
giving it devel_ack+ but also want to make sure that people know that we're not going to fix this retrospectively for older releases. Only RHEL-7.4+
@jstodola: This one came relatively late, but I see a point in fixing it.
(In reply to Lubos Kocman from comment #2)
> giving it devel_ack+ but also want to make sure that people know that we're
> not going to fix this retrospectively for older releases. Only RHEL-7.4+
By the way, should I file same bugreports for all redhat-release-* or we can just do everything in one bugreport?
Hello Jan,
I expect VARIANT and VARIANT_ID to be same for all of main RHEL variants. The issue is that we're using VARIANT while the standardised one is VARIANT_ID.
Lubos
VARIANT and VARIANT_ID are present in /etc/os-release, tested on Snapshot1 with:
redhat-release-server-7.4-15.el7
redhat-release-client-7.4-18.el7
redhat-release-computenode-7.4-14.el7
redhat-release-workstation-7.4-15.el7
Moving to VERIFIED.
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-2017:1850