Bug 2230575 - Don't enable services/timers statically
Summary: Don't enable services/timers statically
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: grub2
Version: 39
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Nicolas Frayer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 2229703 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-09 16:32 UTC by Christian Glombek
Modified: 2023-08-16 08:14 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Fedora Package Sources fedora-release pull-request 274 0 None None None 2023-08-09 16:38:04 UTC
Fedora Package Sources grub2 pull-request 26 0 None None None 2023-08-09 16:56:14 UTC
Github rhboot grub2 pull 131 0 None open Add [Install] section to aux systemd units 2023-08-09 16:33:53 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.