Trigger .autorelabel if there were paths excluded#453
Merged
Conversation
davidcassany
force-pushed
the
trigger_relabel
branch
from
0d61567 to
40a224a
Compare
Contributor
Author
davidcassany
force-pushed
the
trigger_relabel
branch
from
40a224a to
a578e52
Compare
Signed-off-by: David Cassany <dcassany@suse.com>
davidcassany
force-pushed
the
trigger_relabel
branch
from
a578e52 to
664a55a
Compare
frelon
approved these changes
May 26, 2026
ipetrov117
approved these changes
May 27, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This PR generates the /etc/selinux/.autorelabel file if there were some paths excluded during the relaballing at upgrade time. Persistent shared paths are excluded to prevent runtime race conditions. With this change after every upgrade the system gets relabelled at boot (feature provided by
selinux-autorelabelon SUSE systems). Since each snapshot has its own snapshotted /etc the relabelling only happens when the new updated snapshot boots for the first time.