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 1607310 - Incorrect PRETTY_NAME in /etc/os-release
Summary: Incorrect PRETTY_NAME in /etc/os-release
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: redhat-release
Version: 7.0
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: pre-dev-freeze
: ---
Assignee: Luke Meyer
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-23 09:22 UTC by Sandeep
Modified: 2024-03-25 15:06 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-11 21:49:01 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELBLD-4725 0 None None None 2023-09-07 19:18:07 UTC

Description Sandeep 2018-07-23 09:22:26 UTC
Description of problem:

Incorrect PRETTY_NAME in /etc/os-release

Cu is having issues on some of our servers the PRETTY_NAME variable in /etc/os-release is set to OpenShift Enterprise although there is not any OpenShift subscriptions being attached to the server.
He tried removing the file /var/lib/rhsm/branded_name and restarted the brandbot service but that didn't help.

We suggested cu for editing the file /var/lib/rhsm/branded_name and make it null and then re start the brandbot service so that the value can be changed.

But cu is not happy with the answer as an empty branded_name file causes the PRETTY_NAME to be removed completely from /etc/os-release which doesn't correspond to the rest of our servers.

Cu wants the PRETTY_NAME variable to be changed once the subscription is removed from the server.

Kindly guide us on the same.

Comment 2 Lubos Kocman 2018-07-24 11:33:27 UTC
Hello Sandeep,

This seems to be custom redhat-release build done by OpenShift people.
I'll need more information this is how we define pretty name.

%define debug_package %{nil}
%define product_family Red Hat Enterprise Linux
%define variant_titlecase Server
%define variant_lowercase server
%define release_name Maipo
%define base_release_version 7
%define full_release_version 7.6
%define dist_release_version 7
%define beta Beta
%define dist .el%{dist_release_version}
# repo family ensures that productids have more fine versioning. beta,htb,dist
%define repo_family beta

PRETTY_NAME="%{product_family}%{?variant_titlecase: %{variant_titlecase}} %{full_release_version}%{?beta: %{beta}} (%{release_name})"

I'll ask somebody from openshift to move bug correctly under OpenShift wings.

Comment 3 Sandeep 2018-07-24 17:10:44 UTC
Thank you Lubos.

Comment 4 Anushree Agrawal 2019-07-08 16:37:59 UTC
Hello team,

It has been quite a long time we have not received any update on this. 
It would be great if we can get an update on this request.

Regards,
Anushree Agrawal

Comment 6 sgajendr 2020-03-18 11:10:18 UTC
Hello team,

It has been quite a long time we have not received any update on this. 
It would be great if we can get an update on this request.

Regards
Saurabh
Global Support Services
Red Hat

Comment 7 sthangav 2020-03-27 05:21:18 UTC
Moving it to Openshift ART team who are responsible for modifying the file.

Comment 10 Demian Phillips 2020-04-20 15:48:21 UTC
I just inherited a ton of systems that have this in the login screen and they were never openshift and never will run openshift.
Turns out someone used whatever custom iso that was made for openshift to build a "RHEL 7" template in vcenter and then sent jenkins off deploying from it for some time.

Can we just change the pretty name or are all of these systems possibly broken due to openshift specific changes to the OS (why have a special release if it is just normal RHEL)?

Currently these are all pointed to standard RHEL repos in satellite and using normal RHEL licenses.

Comment 11 Dave Carmichael 2020-05-01 20:47:35 UTC
(In reply to Demian Phillips from comment #10)
> I just inherited a ton of systems that have this in the login screen and
> they were never openshift and never will run openshift.
> Turns out someone used whatever custom iso that was made for openshift to
> build a "RHEL 7" template in vcenter and then sent jenkins off deploying
> from it for some time.
> 
> Can we just change the pretty name or are all of these systems possibly
> broken due to openshift specific changes to the OS (why have a special
> release if it is just normal RHEL)?
> 
> Currently these are all pointed to standard RHEL repos in satellite and
> using normal RHEL licenses.

Hi Demian,

It would be difficult to answer without knowing more about what is installed. I recommend opening a case and attaching a sosreport from one of the systems to pursue whether anything needs to be done other than correcting the pretty name.

Kind regards,
Dave Carmichael
Senior Technical Account Manager, Customer Experience and Engagement

Comment 14 Chris Williams 2020-11-11 21:49:01 UTC
Red Hat Enterprise Linux 7 shipped it's final minor release on September 29th, 2020. 7.9 was the last minor releases scheduled for RHEL 7.
From intial triage it does not appear the remaining Bugzillas meet the inclusion criteria for Maintenance Phase 2 and will now be closed. 

From the RHEL life cycle page:
https://access.redhat.com/support/policy/updates/errata#Maintenance_Support_2_Phase
"During Maintenance Support 2 Phase for Red Hat Enterprise Linux version 7,Red Hat defined Critical and Important impact Security Advisories (RHSAs) and selected (at Red Hat discretion) Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available."

If this BZ was closed in error and meets the above criteria please re-open it flag for 7.9.z, provide suitable business and technical justifications, and follow the process for Accelerated Fixes:
https://source.redhat.com/groups/public/pnt-cxno/pnt_customer_experience_and_operations_wiki/support_delivery_accelerated_fix_release_handbook  

Feature Requests can re-opened and moved to RHEL 8 if the desired functionality is not already present in the product. 

Please reach out to the applicable Product Experience Engineer[0] if you have any questions or concerns.  

[0] https://bugzilla.redhat.com/page.cgi?id=agile_component_mapping.html&product=Red+Hat+Enterprise+Linux+7


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