Bug 813200

Summary: SELinux errors with appliance-creator
Product: [Fedora] Fedora Reporter: Marko Myllynen <myllynen>
Component: appliance-toolsAssignee: David Huff <dhuff>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: apevec, dhuff, mattdm, mgoldman, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-10-15 14:44:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Marko Myllynen 2012-04-17 08:32:56 UTC 
Description of problem:
When using appliance-creator with the host SELinux is in Permissive mode, the following errors are being printed (but the appliance image is still being built) - the last SELinux complaint is printed even with selinux --disabled, the former with selinux --permissive / selinux --enforcing.

Removing password for user root.
passwd: Success
Installation finished. No error reported.
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.3.0-0.rc3.git7.2.fc17.x86_64
Found initrd image: /boot/initramfs-3.3.0-0.rc3.git7.2.fc17.x86_64.img
done
/etc/selinux/targeted/contexts/files/file_contexts: line 2352 has invalid
context system_u:object_r:xfs_exec_t:s0
/etc/selinux/targeted/contexts/files/file_contexts: line 2585 has invalid
context system_u:object_r:xfs_exec_t:s0
/etc/selinux/targeted/contexts/files/file_contexts: line 3162 has invalid
context system_u:object_r:xfs_exec_t:s0
/etc/selinux/targeted/contexts/files/file_contexts: line 3610 has invalid
context system_u:object_r:xfs_exec_t:s0
99%
Unmounting directory /var/tmp/imgcreate-9gzrRx/install_root/
Losetup remove /dev/loop0
Finished
umount: /var/tmp/imgcreate-9gzrRx/install_root/sys/fs/selinux/load: not found

See bug 812298 for the example kickstart file if needed.

Version-Release number of selected component (if applicable):
Fedora 17 Beta
Comment 1 Matthew Miller 2012-10-15 14:44:29 UTC 

*** This bug has been marked as a duplicate of bug 812297 ***