Description of problem:
In OpenShift (versions 4.7 - 4.10) we build Red Hat CoreOS using RHEL 8.4 EUS content. We recently picked up systemd-239-45.el8_4.11.x86_64 and one of our systemd units started failing. If we roll back to systemd-239-45.el8_4.10.x86_64 the systemd unit runs fine.
Looking at the change log, we believe Propagate condition failed state to triggering units (#2095950) is causing it. In the path unit, we are checking for changes in a particular directory with `PathChanged`. In the service we are checking for the additioin of a specific file type in that directory with `ConditionPathExistsGlob`. For some reason the path unit is detecting a change (maybe the creation of the directory by systemd-tmpfiles?) and triggering the service, but there are not files in the directory so the service does not run. This gets propagated back up to the path and monitoring of the path is disabled.
Version-Release number of selected component (if applicable):
systemd-239-45.el8_4.11.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Here are the path and service units.
https://github.com/coreos/console-login-helper-messages/blob/v0.20.3/usr/lib/systemd/system/console-login-helper-messages-issuegen.pathhttps://github.com/coreos/console-login-helper-messages/blob/v0.20.3/usr/lib/systemd/system/console-login-helper-messages-issuegen.service
2. On startup, the path unit triggers the service but since there are no `*.issues` in the directory, the service will not start. This is considered a failure and it gets propagated up to the path and the path will no longer monitor the path.
Actual results:
Path unit gets shut down and no longer monitors the path for changes
Expected results:
The service should not be considered failed if the condition to start the unit is not met.
Additional info:
This change was also recently picked up in RHEL 8.6 EUS and is affecting OCP 4.11
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 (systemd 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/RHBA-2022:7727