-
Story
-
Resolution: Unresolved
-
Normal
-
None
-
rhel-10.1
-
None
-
Low
-
rhel-systemd
-
5
-
False
-
False
-
-
None
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
-
All
-
None
What were you trying to do that didn't work?
Our customer would like to see the command `systemctl is-system-running` displaying "degraded" (+ impacted units listed via a dbus property) in order to easily detect ordering cycle problems, as a continuous improvement after merging RHEL-100353 into RHEL 9.7.
The PR in question has been merged recently: https://github.com/systemd/systemd/pull/39210
What is the impact of this issue to you?
Slow down the detection of this kind of problems.
Please provide the package NVR for which the bug is seen:
systemd-252-55.el9.x86_64
How reproducible is this bug?:
Always
Steps to reproduce
- setup a.service running After b.service, the later must also run After a.service to create a simple dependency circle
- Enable them and reboot
- systemctl is-system-running
Expected results
degraded
Actual results
is-running