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

If a customer performs a leapp upgrade where /var/run is a physical directory and not the expected symlink `var/run -> ../run` this can lead to later issues after rebooting during the upgrade.

Related to issue here: https://access.redhat.com/solutions/7079063

What is the impact of this issue to you?

The system either drops to a dracut shell mid-upgrade or has login failures post-upgrade

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

leapp-0.18.0-1.el8_10.noarch.rpm

How reproducible is this bug?:

Reproducible

Steps to reproduce

1.  unlink /var/run
2. mkdir /var/run
3.  Run leapp upgrade
4. reboot and see leapp upgrade completes.
5. Either booting to the RHEL 9 kernel fails with various service failures (audit, network-manager, authorization, dbus) or login fails post-upgrade  (boot to Troubleshooting mode via DVD ISO or use systemd.debug-shell=1)

Expected results

Let's add either an inhibitor or at least a High message warning customers about this unsupported configuration as I think this will improve the customer's experience.

Actual results

Upgrade completes but after rebooting either boot fails or customer unable to login due to PAM failure.