Bug 1914575
| Summary: | grub-boot-success.service should not be started inside systemd-nspawn container | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Gena Makhomed <makhomed> |
| Component: | grub2 | Assignee: | Bootloader engineering team <bootloader-eng-team> |
| Status: | CLOSED ERRATA | QA Contact: | Release Test Team <release-test-team-automation> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 8.3 | CC: | pjanda, pzatko, rharwood |
| Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
| Target Release: | 8.0 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | grub2-2.02-111.el8 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-05-10 15:31:42 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
Gena Makhomed
2021-01-09 22:15:10 UTC
Updated patch to fix this bug: # diff -u /usr/lib/systemd/user/grub-boot-success.timer.orig /usr/lib/systemd/user/grub-boot-success.timer --- /usr/lib/systemd/user/grub-boot-success.timer.orig 2020-09-08 22:00:24.000000000 +0300 +++ /usr/lib/systemd/user/grub-boot-success.timer 2021-01-10 00:11:23.813009897 +0200 @@ -1,5 +1,6 @@ [Unit] Description=Mark boot as successful after the user session has run 2 minutes +ConditionVirtualization=!container ConditionUser=!@system [Timer] Hi,
> grub-boot-success.timer should be disabled inside systemd-nspawn containers.
Could you please indicate what the problem with it is? That is, what is breaking for you?
> Could you please indicate what the problem with it is? That is, what is breaking for you?
"systemctl --user" command show failed service run:
● grub-boot-success.service loaded failed failed Mark boot as successful
grub-boot-success.timer loaded active elapsed Mark boot as successful after the user session has run 2 minutes
it is breaking systemd service monitoring for me.
failed service means what something is wrong with system and it should be repaired.
fix is trivial:
# diff -u /usr/lib/systemd/user/grub-boot-success.timer.orig /usr/lib/systemd/user/grub-boot-success.timer
--- /usr/lib/systemd/user/grub-boot-success.timer.orig 2020-09-08 22:00:24.000000000 +0300
+++ /usr/lib/systemd/user/grub-boot-success.timer 2021-01-10 00:11:23.813009897 +0200
@@ -1,5 +1,6 @@
[Unit]
Description=Mark boot as successful after the user session has run 2 minutes
+ConditionVirtualization=!container
ConditionUser=!@system
[Timer]
P.S. This bug already fixed if Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=1914571 $ cat /usr/lib/systemd/user/grub-boot-success.timer [Unit] Description=Mark boot as successful after the user session has run 2 minutes ConditionUser=!@system ConditionVirtualization=!container [Timer] OnActiveSec=2min Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Low: grub2 security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:2110 |