Bug 860906 - SELinux is preventing /usr/sbin/setfiles from read, write access on the chr_file /dev/mapper/control.
Summary: SELinux is preventing /usr/sbin/setfiles from read, write access on the chr_f...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:0b984051b55b37dcdf65a39c40b...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-27 05:12 UTC by Steve Tyler
Modified: 2012-09-27 10:36 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-09-27 10:36:37 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: type (9 bytes, text/plain)
2012-09-27 05:13 UTC, Steve Tyler
no flags Details
File: hashmarkername (14 bytes, text/plain)
2012-09-27 05:13 UTC, Steve Tyler
no flags Details
File: description (2.93 KB, text/plain)
2012-09-27 05:13 UTC, Steve Tyler
no flags Details

Description Steve Tyler 2012-09-27 05:12:30 UTC
Additional info:
libreport version: 2.0.12
kernel:         3.6.0-0.rc6.git0.2.fc18.x86_64

Comment 1 Steve Tyler 2012-09-27 05:13:23 UTC
Created attachment 617898 [details]
File: type

Comment 2 Steve Tyler 2012-09-27 05:13:25 UTC
Created attachment 617899 [details]
File: hashmarkername

Comment 3 Steve Tyler 2012-09-27 05:13:28 UTC
Created attachment 617900 [details]
File: description

Comment 4 Steve Tyler 2012-09-27 05:29:25 UTC
This occurred near the end of a test install from a Live CD in a VM.

anaconda-18.10-1.fc18
https://admin.fedoraproject.org/updates/anaconda-18.10-1.fc18

Fedora-18-Nightly-20120924.09-x86_64-Live-desktop.iso
http://koji.fedoraproject.org/koji/taskinfo?taskID=4520439

$ qemu-kvm -m 2048 -hda f18-test-2.img -cdrom ~/xfr/fedora/nightly-composes/Fedora-18-Nightly-20120924.09-x86_64-Live-desktop.iso -vga qxl -boot menu=on -usbdevice mouse

Comment 5 Miroslav Grepl 2012-09-27 10:36:37 UTC
It should be fixed with the latest policy which is not a part of this image.


Note You need to log in before you can comment on or make changes to this bug.