Bug 2005552
| Summary: | redhat-release should enable greenboot services in preset | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Xiaofeng Wang <xiaofwan> |
| Component: | redhat-release | Assignee: | Stephen Gallagher <sgallagh> |
| Status: | CLOSED ERRATA | QA Contact: | Release Test Team <release-test-team-automation> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 9.0 | CC: | lisas, perobins, pzatko, xiaofwan, yih |
| Target Milestone: | rc | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | redhat-release-9.0-2.9.el9 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-05-17 15:35:34 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
Xiaofeng Wang
2021-09-18 04:34:48 UTC
ACKed from a RHEL for Edge development PoV Stephen, assigning to you for change to be made in CentOS and 9 GA. Hi Stephen! Which Internal Target Milestone should I use? What's your plan? Thanks. I'm setting these based on my own expectation of when they will be done. Thanks Stephen! Verified on redhat-release-9.0-2.9.el9.x86_64. [admin@localhost ~]$ sudo systemctl is-enabled greenboot-grub2-set-counter greenboot-grub2-set-success greenboot-healthcheck greenboot-rpm-ostree-grub2-check-fallback greenboot-status greenboot-task-runner redboot-auto-reboot redboot-task-runner enabled enabled enabled enabled enabled enabled enabled enabled [admin@localhost ~]$ journalctl -b -0 -u boot-complete.target -u greenboot -u greenboot-healthcheck -u greenboot-rpm-ostree-grub2-check-fallback -u greenboot-grub2-set-counter -u greenboot-grub2-set-success -u greenboot-status -u redboot -u redboot-auto-reboot -u redboot.target -- Journal begins at Wed 2021-11-03 00:19:52 EDT, ends at Wed 2021-11-03 02:49:29 EDT. -- Nov 03 00:19:57 localhost.localdomain systemd[1]: Starting Check for fallback boot... Nov 03 00:19:57 localhost.localdomain systemd[1]: Finished Check for fallback boot. Nov 03 00:19:57 localhost.localdomain systemd[1]: Starting greenboot Health Checks Runner... Nov 03 00:19:57 localhost.localdomain greenboot[709]: Running Required Health Check Scripts... Nov 03 00:19:57 localhost.localdomain 00_required_scripts_start.sh[716]: Running greenboot Required Health Check Scripts Nov 03 00:19:57 localhost.localdomain greenboot[709]: Script '00_required_scripts_start.sh' SUCCESS Nov 03 00:19:57 localhost.localdomain greenboot[709]: Running Wanted Health Check Scripts... Nov 03 00:19:57 localhost.localdomain 00_wanted_scripts_start.sh[723]: Running greenboot Wanted Health Check Scripts Nov 03 00:19:57 localhost.localdomain greenboot[709]: Script '00_wanted_scripts_start.sh' SUCCESS Nov 03 00:19:57 localhost.localdomain systemd[1]: Finished greenboot Health Checks Runner. Nov 03 00:19:57 localhost.localdomain systemd[1]: Reached target Boot Completion Check. Nov 03 00:19:57 localhost.localdomain systemd[1]: Starting Mark boot as successful in grubenv... Nov 03 00:19:57 localhost.localdomain systemd[1]: Finished Mark boot as successful in grubenv. Nov 03 00:19:57 localhost.localdomain systemd[1]: Starting greenboot MotD Generator... Nov 03 00:19:57 localhost.localdomain greenboot-status[753]: Boot Status is GREEN - Health Check SUCCESS Nov 03 00:19:57 localhost.localdomain systemd[1]: Finished greenboot MotD Generator. Thank you Xiaofeng. Moving to VERIFIED as per comment 11 and comment 12 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 (new packages: redhat-release), 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/RHBA-2022:3893 |