Hide Forgot
Description of problem: In rhel7 we have a tool name brandbot which modifies pretty_name in /etc/os-release to correspond to the actual product name customers bought to the user. Unfortunately /etc/os-release is not marked as a configuration file, so this change will be overwritten by the next update of redhat-release. Please note that this change should be done in all redhat-release-* packages. diff --git a/redhat-release-server.spec b/redhat-release-server.spec index 152abc9..fbddf1a 100644 --- a/redhat-release-server.spec +++ b/redhat-release-server.spec @@ -100,7 +100,7 @@ rm -rf $RPM_BUILD_ROOT %defattr(0644,root,root,0755) /etc/redhat-release /etc/system-release -/etc/os-release +%config(noreplace) /etc/os-release %config /etc/system-release-cpe %config(noreplace) /etc/issue %config(noreplace) /etc/issue.net
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.
This is closed already, but related to https://bugzilla.redhat.com/show_bug.cgi?id=1257142 I think this is could be NOTABUG. A redhat-release-* update overwriting /etc/os-release is ok. If the system is using subscriptions with branding info, subscriptions-manager and brandbot will update it to the branded name at the first opportunity (which is typically the next time entitlement certs are updated, either via subscription-manager user interaction or automatically via rhsmcertd). So PRETTY_NAME could stay unbranded for some time period, but I think that's acceptable. If needed more immediately redhat-release-* could poke brandbot.service in post (or updated /var/lib/rhsm/branded_name so brandbot.path triggers, etc).