Closed c4rt0 closed 1 week ago
In the logs I see:
Would relabel /var/cache/systemd from system_u:object_r:var_t:s0 to system_u:object_r:systemd_cache_t:s0
Would relabel /var/cache/systemd/home from system_u:object_r:var_t:s0 to system_u:object_r:systemd_homed_cache_t:s0
Probably the policy has just changed for these files and we need to add exceptions to our test for them.
Yes, the labels on the existing files (in /var
) are not updated when the association changes in the policy.
Yes, the labels on the existing files (in
/var
) are not updated when the association changes in the policy.
I wonder if that ever causes problems on upgrading systems? i.e. basically the policy has to allow for the older default labels forever?
Upstream change that caused this:
This should be handled by https://github.com/coreos/fedora-coreos-config/pull/3225
kola-upgrade builds fail with
Unexpected mislabeled file found: /var/cache/systemd
,Unexpected mislabeled file found: /var/cache/systemd/home
:From console.txt:
console.txt journal.txt