What were you trying to do that didn't work?

Our customer gets units generated using /usr/lib/systemd/system-generators/podman-system-generator which belongs to a podman package. Here is an except of a generated unit that can introduce a dependency cycle:

[Unit]
Description=viewz-ui yaml based service
Before=local-fs.target <<<
After=network-online.target <<<
Wants=network-online.target
SourcePath=/etc/containers/systemd/viewz-ui.kube
RequiresMountsFor=%t/containers

This unit in installed / WantedBy multi-user.target. But they cannot use `systemd-analyze verify multi-user.target` (or in specifying the new unit) in order to check whether problems are identified in these generated units.

Stracing systemd-analyze shows that it does not inspect /run/systemd/generator.

What is the impact of this issue to you?

Cannot easily identify the culprit when a dependency cycle is introduced by a generated unit.

Please provide the package NVR for which the bug is seen:

systemd-239-82.el8_10.1.x86_64

How reproducible is this bug?:

Always for the customer. Didn't reproduce internally with the podman generator.

Expected results

systemd-analyze verify multi-user.target raises the problems regarding a generated unit.

Actual results

systemd-analyze verify multi-user.target does not raise the problems regarding a generated unit.