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.

Bug 950373

Summary: Please support /etc/os-release
Product: Red Hat Enterprise Linux 7 Reporter: Jakub Filak <jfilak>
Component: redhat-releaseAssignee: Daniel Mach <dmach>
Status: CLOSED CURRENTRELEASE QA Contact: Release Test Team <release-test-team-automation>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: dgregor, jberan, jmoskovc, lpoetter, mbanas, mganisin, mjc, rvokal
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-13 12:00:58 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:
Bug Depends On:    
Bug Blocks: 958741    

Description Jakub Filak 2013-04-10 07:27:47 UTC
Description of problem:
Various projects (ABRT, systemd) expects that /etc/os-release exists.

Additional info:
See bug #733117 for details

Comment 4 Lennart Poettering 2013-04-10 12:49:40 UTC
It might make sense to add ID_LIKE=fedora. If you decide to use ID=rhel-client, then you also should add ID_LIKE=rhel.

Also:

HOME_URL="https://www.redhat.com/products/enterprise-linux/"
SUPPORT_URL="https://access.redhat.com/home"
BUG_REPORT_URL="https://bugzilla.redhat.com/"

Or something like that.

For a full explanation of the available fields see the man page:

http://www.freedesktop.org/software/systemd/man/os-release.html

Comment 5 Lennart Poettering 2013-04-10 12:52:39 UTC
This bug is reported against "rhel-release-server", but the suggestion in #2 talk of the client. I am confused...

Comment 7 Daniel Mach 2013-04-10 13:27:01 UTC
(In reply to comment #5)
> This bug is reported against "rhel-release-server", but the suggestion in #2
> talk of the client. I am confused...

All the redhat-release-%variant packages are same, the only difference is the variant name. Sorry for confusion.

Comment 8 Bill Nottingham 2013-04-10 15:10:50 UTC
CC'ing Mark Cox for comments on the CPE name. Note that this file will likely be edited post-install due to the flexible branding feature.

Comment 9 Lennart Poettering 2013-04-10 20:56:20 UTC
(In reply to comment #6)
> It would be nice to provide fields useful for bug reporting.
> 
> For example:
> BUGZILLA_PRODUCT="Red Hat Enterprise Linux 7"
> RHSUPPORT_PRODUCT_VERSION="7.0 Alpha"

That sounds a bit too specific to support in generic fields. However, the file is extensible, and vendors can add their own keys prefixed by some vendor ID. Hence, if RH decides to add some fields they should probably be:

REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 7"
REDHAT_SUPPORT_PRODUCT_VERSION="7.0 Alpha"

Comment 10 Mark J. Cox 2013-04-11 09:32:04 UTC
Including the CPE means we really could get rid of the /etc/cpe* file which never really gained traction outside of Red Hat anyway.  

CPE_NAME="cpe:/o:redhat:enterprise_linux:7.0.0:beta:client"

Would be accurate.

Comment 11 Jakub Filak 2013-05-02 08:25:41 UTC
(In reply to comment #9)
I've added support for the following fields in ABRT:
  REDHAT_BUGZILLA_PRODUCT
  REDHAT_BUGZILLA_PRODUCT_VERSION
  REDHAT_SUPPORT_PRODUCT
  REDHAT_SUPPORT_PRODUCT_VERSION

https://github.com/abrt/libreport/commit/a38367c1bd648a46125b2dc799046d210c567c40

Comment 12 Lennart Poettering 2013-07-08 21:47:24 UTC
Just to mention this: this looks like an OK use of os-release and extension fields to me. Of course, I'd prefer if the primary os-release fields and the bugzilla components could always stay in sync, but if that's not possible, then storing the difference in vendor-specific extension fields sounds like an OK solution, especially given that other vendors such as SUSE or Mageia have a very different bugzilla architecture and hence there's nothing to unify there.

Comment 16 Ludek Smid 2014-06-13 12:00:58 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.