Description of problem: On Fedora Atomic Host rawhide, /usr/bin/docker-storage-setup has a selinux context of system_u:object_r:bin_t:s0 but it had a context of system_u:object_r:container_runtime_exec_t:s0 in F24 and F25. If the context has changed, I can update the test to reflect it. Steps to reproduce: 1. Boot any fedora atomic host 2. ostree remote add --no-gpg-verify custom https://kojipkgs.fedoraproject.org/atomic/rawhide/ 3. rpm-ostree rebase custom:fedora/rawhide/x86_64/atomic-host 55a65a66f736e7637a23ddb9b649546d7b4ea247c35e32f61047dc7882d08a93 4. systemctl reboot 5. Reconnect 6. ls -Z /usr/bin/docker-storage-setup [cloud-user@fedora ~]$ ls -Z /usr/bin/docker-storage-setup system_u:object_r:bin_t:s0 /usr/bin/docker-storage-setup Ostree Info: Version: Rawhide.20170824.n.0 (2017-08-24 14:35:23) Commit: 55a65a66f736e7637a23ddb9b649546d7b4ea247c35e32f61047dc7882d08a93
I think bin_t is expected: https://github.com/projectatomic/atomic-host-tests/issues/133 I think we just need to update the tests to check for the same value as what is in f26.
I'll close this bug out and update the test.
This should fix it: https://github.com/projectatomic/atomic-host-tests/pull/236