ansible: Fix podman socket SELinux context on AWS #631
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Argh, retried with fresh deployment, and still broken. 🤯 |
|
This works on Fedora CoreOS, but not on Fedora 40 rpm on PSI: 🤯 |
On Fedora CoreOS, SELinux wants the socket path in /run, while on Fedora 40 (on our PSI runners) it wants to go via /var/run, due to the conflicting "extra_varrun" custom policy that Fedora installs for migration. Adjust the policy for /run (see [1] and bump priority to avoid conflicting with extra_varrun. [1] https://discussion.fedoraproject.org/t/f40-change-proposal-move-var-run-selinux-policy-entries-to-run-self-contained/100171
|
Finally! This works. Completely coincidentally, that will also help me for https://issues.redhat.com/browse/RHEL-70238 |
jelly
approved these changes
Dec 6, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
On Fedora CoreOS, SELinux wants the socket path in /run, while on Fedora
40 (on our PSI runners) it wants to go via /var/run, due to the
conflicting "extra_varrun" custom policy that Fedora installs for
migration.
Adjust the policy for /run (see [1] and bump priority to avoid
conflicting with extra_varrun.
[1] https://discussion.fedoraproject.org/t/f40-change-proposal-move-var-run-selinux-policy-entries-to-run-self-contained/100171
See https://github.com/orgs/cockpit-project/projects/4/?pane=issue&itemId=69115598 . Tested on PSI and AWS.