Add inhibitor for incorrect /var/run symlink configuration#1546
Add inhibitor for incorrect /var/run symlink configuration#1546prjagtap-rh wants to merge 1 commit into
Conversation
Thank you for contributing to the Leapp project!Please note that every PR needs to comply with the leapp-repository contribution and development guidelines and must pass all tests in order to be mergeable.
Packit will automatically schedule regression tests for this PR's build and latest upstream leapp build.
Note that first time contributors cannot run tests automatically - they need to be started by a reviewer. It is possible to schedule specific on-demand tests as well. Currently 2 test sets are supported,
See other labels for particular jobs defined in the Please open ticket in case you experience technical problem with the CI. (RH internal only) Note: In case there are problems with tests not being triggered automatically on new PR/commit or pending for a long time, please contact leapp-infra. |
ba4c2d4 to
80f1e8e
Compare
80f1e8e to
f7a6375
Compare
In modern Linux systems that use systemd, /run is a tmpfs filesystem managed by systemd and /var/run must be a symbolic link pointing to ../run for compatibility. Inhibit the upgrade if /var/run is not configured as expected, as this can cause boot failures, service startup failures, or login issues. Extended the FileInfo model with a real_path field and add /var/run to the scansourcefiles tracked files list. The ChecksPhase actor consumes the TrackedFilesInfoSource message to detect this unsupported configuration and inhibits the upgrade. JIRA: RHEL-76846
f7a6375 to
8ddb8fc
Compare
If /var/run is not correctly configured as a symbolic link to /run, the in-place upgrade can lead to boot failures, service startup failures, or login issues. A new ChecksPhase actor detects this unsupported configuration and inhibits the upgrade.
JIRA: RHEL-76846