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 1359645 - Brandbot cannot be disabled
Brandbot cannot be disabled
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: redhat-release (Show other bugs)
7.2
Unspecified Unspecified
urgent Severity high
: rc
: ---
Assigned To: Lubos Kocman
Release Test Team
:
Depends On: 1357648
Blocks: ovirt-node-ng-43-platform
  Show dependency tree / graph
 
Reported: 2016-07-25 04:20 EDT by Lukáš Nykrýn
Modified: 2017-08-01 13:29 EDT (History)
11 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1357648
Environment:
Last Closed: 2017-08-01 13:29:54 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-2017:1850 normal SHIPPED_LIVE redhat-release update 2017-08-01 14:03:01 EDT

  None (edit)
Comment 1 Lubos Kocman 2017-01-12 07:54:35 EST 
This is reasonable, dev_acking

Lubos
Comment 2 Lubos Kocman 2017-03-06 11:42:20 EST 
Enabled brandbot.* on all variants in 90-default.preset

Lubos
Comment 4 Peter Kotvan 2017-05-02 06:51:05 EDT 
It does not make sense to set it as enabled in 90-default.preset since the unit is "static" right now.

See [1]: "static" - The unit file is not enabled, and has no provisions for enabling in the "[Install]" unit file section.

The unit file has to be modified accordingly to allow its disabling using "systemctl disable".

[1] https://www.freedesktop.org/software/systemd/man/systemctl.html
Comment 5 Peter Kotvan 2017-05-02 07:06:59 EDT 
Changing component to initscripts.
Comment 12 errata-xmlrpc 2017-08-01 13:29:54 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-2017:1850
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.