Bug 1382308 - disable rhsmcertd in systemd presets [NEEDINFO]
Summary: disable rhsmcertd in systemd presets
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: redhat-release
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Lubos Kocman
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks: 1201663
TreeView+ depends on / blocked
 
Reported: 2016-10-06 10:22 UTC by Frantisek Kluknavsky
Modified: 2018-04-17 13:57 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-27 13:10:25 UTC
Target Upstream Version:
fkluknav: needinfo? (lkocman)

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

Description Frantisek Kluknavsky 2016-10-06 10:22:55 UTC 
Description of problem:
rhsmcertd.service is missing in systemd preset file.
(see https://bugzilla.redhat.com/show_bug.cgi?id=1209382)

Version-Release number of selected component (if applicable):
7.3-3

Steps to Reproduce:
1. cat /usr/lib/systemd/system-preset/90-default.preset | grep rhsmcertd.service

Actual results:
not found

Expected results:
disable rhsmcertd.service
Comment 1 Frantisek Kluknavsky 2016-10-06 10:39:37 UTC 
Also, a lot of other enabled services do not make much sense in a container. If you happen to install them to satisfy some dependecy, you probably do not want to run them. Display managers, tuned, kdump...
Comment 3 Frantisek Kluknavsky 2016-10-06 14:47:05 UTC 
To clarify, this only applies to redhat-release-container. Other redhat-releases should probably enable rhsmcertd.
Comment 5 Frantisek Kluknavsky 2017-02-27 18:08:31 UTC 
Any explanation, alternative, workaround, vision of our future? This looks like The One Best Cloud Container Operating System Company does not actually want to tune its operating system for container deployments. I am quite sure it must be a misunderstanding.
Note You need to log in before you can comment on or make changes to this bug.