Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1896929

Summary:	systemd complains about Unit configured to use KillMode=none
Product:	[Fedora] Fedora	Reporter:	Orion Poplawski <orion>
Component:	plymouth	Assignee:	Ray Strode [halfline] <rstrode>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	33	CC:	bilias, cdennett, dapmeup, gnome-sig, hdegoede, jh.xsnrg, jwadodson, pwhalen, rstrode
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	plymouth-0.9.5-1.20210323git8a3c9bb.fc34	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-03-28 00:15:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Orion Poplawski 2020-11-11 21:48:14 UTC

Description of problem:

/usr/lib/systemd/system/plymouth-start.service:15: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed

Version-Release number of selected component (if applicable):
plymouth-0.9.4-16.20200325gite31c81f.fc33.x86_64
systemd-246.6-3.fc33.x86_64

Comment 1 John Dodson 2021-01-28 12:34:44 UTC

So should it be 'mixed' or 'control-group' what are the effects of each for plymouth & systemd?

Comment 2 Hans de Goede 2021-02-23 21:34:23 UTC

*** Bug 1931682 has been marked as a duplicate of this bug. ***

Comment 3 Fedora Update System 2021-03-23 13:35:19 UTC

FEDORA-2021-ebde0e7e8a has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-ebde0e7e8a

Comment 4 Fedora Update System 2021-03-24 02:44:32 UTC

FEDORA-2021-ebde0e7e8a has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-ebde0e7e8a`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-ebde0e7e8a

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Hans de Goede 2021-03-25 11:39:01 UTC

*** Bug 1889923 has been marked as a duplicate of this bug. ***

Comment 6 Fedora Update System 2021-03-28 00:15:23 UTC

FEDORA-2021-ebde0e7e8a has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.