Bug 2229703

Summary: grub2-boot-success.timer cannot be disabled
Product: [Fedora] Fedora Reporter: Sayan <saypaul>
Component: grub2Assignee: Nicolas Frayer <nfrayer>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: rawhideCC: akoutsou, fmartine, lkundrak, miabbott, mlewando, nfrayer, pjones, rharwood
Target Milestone: ---Keywords: AutomationBlocker, Embedded, Improvement, RFE
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-08-09 20:20:24 UTC 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 Sayan 2023-08-07 11:05:00 UTC
grub-boot-success.timer cannot be disabled as it is statically linked, this is causing issue for edge devices (Image based OS) which uses greenboot custom health-check to measure boot success.
The timer can be helpful for desktop related operation but for headless operation it doesn't make much sense, so another suggestion can be to move timer to a separate sub-package which edge device can choose not to install to.

Reproducible: Always

Steps to Reproduce:
1. Install rhel for edge system with presets added in /usr/lib/systemd/user-preset/50-osbiuld.preset "disable grub-boot-success.timer"
2. add a script with "exit 1" in /etc/greenboot/check/required.d/
3. restart 
4. ssh into system and instantly validate the boot_success flag
5. check systemctl --user status grub-boot-success.timer
6. wait for two minute.
7. validate the boot_success flag
Actual Results:  
1. systemctl --user status grub-boot-success.timer shows as active
2. boot_success flag changes fro 0 to 1.


Expected Results:  
1. grub-boot-success.timer to be disabled
2. boot_success not to change from 0 to 1 after two mins.

additional issue details: https://github.com/fedora-iot/greenboot/issues/108

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

*** This bug has been marked as a duplicate of bug 2230575 ***