Bug 1157227 - vdsm does not set selinux booleans during installation when selinux disabled
Summary: vdsm does not set selinux booleans during installation when selinux disabled
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm
Version: 3.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: 3.4.4
Assignee: Yaniv Bronhaim
QA Contact: Ilanit Stein
URL:
Whiteboard: infra
Depends On: 1157185
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-26 11:08 UTC by rhev-integ
Modified: 2016-02-10 19:45 UTC (History)
13 users (show)

Fixed In Version: vdsm-4.14.18-1.el6ev
Doc Type: Bug Fix
Doc Text:
Clone Of: 1157185
Environment:
Last Closed: 2014-12-02 20:27:43 UTC
oVirt Team: Infra
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:1946 0 normal SHIPPED_LIVE vdsm 3.4.4 bug fix and enhancement update 2014-12-03 01:26:44 UTC
oVirt gerrit 34445 0 master MERGED tool: moving setup booleans verb to be part of the configurators Never
oVirt gerrit 34463 0 ovirt-3.5 MERGED tool: moving setup booleans verb to be part of the configurators Never

Comment 1 Eyal Edri 2014-10-28 14:10:32 UTC 
moving to 3.4.4 after approval from vdsm maintainer ybronheim.
Comment 2 Ilanit Stein 2014-11-09 15:34:31 UTC 
Verified on av13, vdsm vdsm-4.14.18-1.el6ev.x86_64

Installed vdsm on 2 rhel6.5 hosts. One host selinux enforced, and the other Permissive.

Both hosts had these selinux booleans (expected values):
# getsebool -a | grep virt
virt_use_comm --> off
virt_use_execmem --> off
virt_use_fusefs --> on
virt_use_nfs --> on
virt_use_samba --> on
virt_use_sanlock --> on
virt_use_sysfs --> on
virt_use_usb --> on
virt_use_xserver --> off

On both hosts, start VM PASS.
Comment 4 errata-xmlrpc 2014-12-02 20:27:43 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2014-1946.html
Note You need to log in before you can comment on or make changes to this bug.