Why systemd logs so many messages with "skipped because of a failed condition check" in RHEL9?

Solution Verified - Updated -

Issue

  • Why systemd logs so many messages with "skipped because of a failed condition check" in RHEL9 which was not seen on RHEL8?
# journalctl -b|grep 'failed condition check'
Sep 16 02:33:37 localhost systemd[1]: Create System Users was skipped because of a failed condition check (ConditionNeedsUpdate=/etc).
Sep 16 02:33:38 localhost systemd[1]: nm-initrd.service was skipped because of a failed condition check (ConditionPathExists=/run/NetworkManager/initrd/neednet).
Sep 16 02:33:38 localhost systemd[1]: nm-wait-online-initrd.service was skipped because of a failed condition check (ConditionPathExists=/run/NetworkManager/initrd/neednet).
Sep 16 02:33:39 localhost systemd[1]: Kernel Module supporting RPCSEC_GSS was skipped because of a failed condition check (ConditionPathExists=/etc/krb5.keytab).
Sep 16 02:33:39 localhost systemd[1]: First Boot Wizard was skipped because of a failed condition check (ConditionFirstBoot=yes).
Sep 16 02:33:39 localhost systemd[1]: First Boot Complete was skipped because of a failed condition check (ConditionFirstBoot=yes).
Sep 16 02:33:40 localhost systemd[1]: First Boot Wizard was skipped because of a failed condition check (ConditionFirstBoot=yes).
Sep 16 02:33:40 localhost systemd[1]: First Boot Complete was skipped because of a failed condition check (ConditionFirstBoot=yes).
Sep 16 02:33:40 localhost systemd[1]: Mark the need to relabel after reboot was skipped because of a failed condition check (ConditionSecurity=!selinux).
Sep 16 02:33:40 localhost systemd[1]: Commit a transient machine-id on disk was skipped because of a failed condition check (ConditionPathIsMountPoint=/etc/machine-id).
Sep 16 02:33:40 localhost systemd[1]: Load CPU microcode update was skipped because of a failed condition check (ConditionPathExists=/sys/devices/system/cpu/microcode/reload).
Sep 16 02:33:41 localhost systemd[1]: RPC security service for NFS client and server was skipped because of a failed condition check (ConditionPathExists=/etc/krb5.keytab).
Sep 16 02:33:41 localhost.localdomain systemd[1]: Run Insights Client at boot was skipped because of a failed condition check (ConditionPathExists=/etc/insights-client/.run_insights_client_next_boot).
Sep 16 02:33:48 localhost.localdomain systemd[939]: Mark boot as successful after the user session has run 2 minutes was skipped because of a failed condition check (ConditionUser=!@system).

Environment

  • Red Hat Enterprise Linux 9.

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content