Bug 2230575

Summary:	Don't enable services/timers statically
Product:	[Fedora] Fedora	Reporter:	Christian Glombek <cglombek>
Component:	grub2	Assignee:	Nicolas Frayer <nfrayer>
Status:	NEW ---	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	39	CC:	fmartine, lkundrak, miabbott, mlewando, nfrayer, pgnd, pjones, rharwood, saypaul
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Christian Glombek 2023-08-09 16:32:44 UTC

Currently in Fedora, the following systemd units are enabled statically by shipping symlinks in the RPM.

- grub-boot-indeterminate.service
- grub-boot-success.timer
- grub-systemd-integration.service

The only way to disable these units is to delete the symlinks manually.

This is problematic in Fedora IoT, where grub-boot-success.timer is
not supposed to be enabled, see https://github.com/fedora-iot/greenboot/issues/108


I propose the following (I'll open the PRs):
- Add an `[Install]` section to these systemd units so that they can be enabled dynamically via presets or manually via systemctl.
- Add presets to enable these services
- Change the grub specfile to not ship the symlinks but instead use the usual systemd macros



Reproducible: Always

Comment 1 Micah Abbott 2023-08-09 20:20:24 UTC

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

Comment 2 Fedora Release Engineering 2023-08-16 08:14:07 UTC

This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle.
Changing version to 39.