Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1357648 - Brandbot cannot be disabled
Brandbot cannot be disabled
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: initscripts (Show other bugs)
7.2
All Linux
medium Severity high
: rc
: ---
Assigned To: David Kaspar [Dee'Kej]
Daniel Rusek
:
Depends On: 1395391 1493545
Blocks: 1380361 ovirt-node-ng-43-platform 1465901 ovirt-node-ng-platform 1359645
  Show dependency tree / graph
 
Reported: 2016-07-18 14:38 EDT by Ryan Barry
Modified: 2018-04-10 14:26 EDT (History)
10 users (show)

See Also:
Fixed In Version: initscripts-9.49.40-2.el7
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1359645 (view as bug list)
Environment:
Last Closed: 2018-04-10 14:24:45 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0983 None None None 2018-04-10 14:26 EDT

  None (edit)
Description Ryan Barry 2016-07-18 14:38:14 EDT 
Description of problem:
Brandbot aggressively rewrites PRETTY_NAME, and here is no way to disable brandbot's behavior other than masking systemd units.

Version-Release number of selected component (if applicable):
initscripts-9.49.30-1.el7_2.2

How reproducible:
100%

Steps to Reproduce:
1. Install any system which does not have a branded "OS", but sets PRETTY_NAME (RHV-H, for example)
2. Register to an account which has an entitlement for a branded "OS", or even "echo foobar > /var/lib/rhsm/branded_name"

Actual results:
3. PRETTY_NAME is overwritten
4. The only way to disable this is to disable/mask brandbot.[path|service]

Expected results:
There should be a way to disable brandbot. Even if this way is changing brandbot to an actual activated service, instead of one which is disabled and triggered by brandbot.path in some way.
Comment 2 Fabian Deutsch 2016-07-18 15:11:08 EDT 
Another considertaion would be to make the behavior - rewrite PRETTY_NAME - configurable.

Disabling brandbot completely might be pretty invasive (not sure what else functionality brandbot is porviding).
Comment 3 Lukáš Nykrýn 2016-07-19 03:06:48 EDT 
That is the only thing that brandbot is doing. TO be host, I have no idea if we want the possibility for user to "easily" disable brandbot. This goes beyond engineering. Let's try to ask someone who was behind this feature for rhel7. https://mojo.redhat.com/docs/DOC-186259
Comment 4 Adrian Likins 2016-07-22 13:21:29 EDT 
> (In reply to Fabian Deutsch from comment #2)

> Disabling brandbot completely might be pretty invasive (not sure what else
> functionality brandbot is porviding).

I don't work on subscription-manager/entitlements anymore, so current team would be better to ask ('chainsaw' team, aka candleping/subscription-manager dev team https://mojo.redhat.com/docs/DOC-19860).


I doubt anyone would notice if it was disabled to be honest, but that is not really my call anymore ;->

Updating PRETTY_NAME is pretty much the only functionality provided by brandbot.
The purpose of brand bot was to provide a way to change things like /etc/issue for RHEL to reflect more specific products/subscriptions/entitlements.

ie, so if I bought 'Red Hat Enterprise Linux Server (Super Turbo Bundle Edition)', the 'bits' for RHEL are the same as every other RHEL Server (69.pem) version so the default PRETTY_NAME is "Red Hat Enterprise Linux Server", but the subscription/product wants PRETTY_NAME to be 'Red Hat Enterprise Linux Server (Super Turbo Bundle Edition)'.

That info is included in the entitlement certificate and subscription-manager/rhsmcertd will update /var/lib/rhsm/branded_name causing the brandbot.path service to trigger /usr/libexec/initscripts/brandbot that changes /etc/os-release.

AFAIK, it is for purely cosmetic purposes (in the sense that nothing really depends on the value of PRETTY_NAME, at least nothing entitlement related). If there are tools that make decisions based on PRETTY_NAME brandbot will likely confuse them.
Comment 5 Lukáš Nykrýn 2016-07-25 04:16:00 EDT 
Ok, let's create a clone for redhat-release-* packages to request adding brandbot* to presets and then make it disableable.
Comment 8 David Kaspar [Dee'Kej] 2017-09-20 09:31:36 EDT 
Pull-request to fix BZ #1395391 submitted for review:
https://github.com/fedora-sysv/initscripts/pull/128

This pull-request also fixes this issue.
Comment 17 errata-xmlrpc 2018-04-10 14:24:45 EDT 
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-2018:0983
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.