Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1485055 - incorrect selinux context for /usr/bin/docker-storage-setup
Summary: incorrect selinux context for /usr/bin/docker-storage-setup
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: rawhide
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lukas Vrabec
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: AcceptedBlocker abrt_hash:6273a4068d4...
Depends On: 1451379 1485050
Blocks: F27FinalBlocker
TreeView+ depends on / blocked
 
Reported: 2017-08-24 22:35 UTC by Michael Nguyen
Modified: 2017-08-25 05:13 UTC (History)
29 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1485050
Environment:
Last Closed: 2017-08-24 23:15:36 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Michael Nguyen 2017-08-24 22:35:32 UTC 
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
Comment 1 Dusty Mabe 2017-08-24 23:12:18 UTC 
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.
Comment 2 Michael Nguyen 2017-08-24 23:15:36 UTC 
I'll close this bug out and update the test.
Comment 3 Dusty Mabe 2017-08-24 23:25:01 UTC 
This should fix it:
https://github.com/projectatomic/atomic-host-tests/pull/236
Note You need to log in before you can comment on or make changes to this bug.