Bug 894071 - [F18] SELinux problems
Summary: [F18] SELinux problems
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-node
Version: 3.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Joey Boggs
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 894059
TreeView+ depends on / blocked
 
Reported: 2013-01-10 16:07 UTC by Fabian Deutsch
Modified: 2016-04-27 02:49 UTC (History)
7 users (show)

Fixed In Version: 2.6.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-06 13:59:15 UTC
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)

Description Fabian Deutsch 2013-01-10 16:07:10 UTC
Description of problem:

Listing /usr/share/virt-manager/virtManagerTui ...
Listing /usr/share/virt-manager/virtManagerTui/importblacklist ...
Configuring SELinux
make: /usr/share/selinux/devel/Makefile: No such file or directory
make: *** No rule to make target `/usr/share/selinux/devel/Makefile'.  Stop.
semodule:  Failed on ovirt.pp!
Attempting to install module 'ovirt.pp':
Fixing boot menu
/home/jenkins/workspace/ovirt-node-iso-devel/ovirt-cache/node-creator-x86_64-tmp/imgcreate-UU4Y3j/install_root/tmp/ks-script-wP305J: line 95: /home/jenkins/workspace/ovirt-node-iso-devel/ovirt-cache/node-creator-x86_64-tmp/imgcreate-UU4Y3j/iso-IC7dhs/EFI/BOOT/BOOTX64.conf: No such file or directory
ignoring %post failure (code 1)

/usr/share/info/dir: could not read (No such file or directory) and could not create (No such file or directory)
Removing python source files

Creating manifest....done
/etc/selinux/targeted/contexts/files/file_contexts: line 1521 has invalid context system_u:object_r:fetchmail_log_t:s0
/etc/selinux/targeted/contexts/files/file_contexts: line 2361 has invalid context system_u:object_r:radiusd_unit_file_t:s0



Version-Release number of selected component (if applicable):
http://jenkins.ovirt.org/job/ovirt-node-iso-devel/1422/console

Comment 2 Mike Burns 2013-02-06 13:59:15 UTC
Patches merged, available in next release


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