Bug 234777 - selinux policy prevents VM accessing bridged network
selinux policy prevents VM accessing bridged network
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: selinux-policy (Show other bugs)
rawhide
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Walsh
Ben Levenson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-04-01 18:18 EDT by Andy Burns
Modified: 2007-11-30 17:12 EST (History)
2 users (show)

See Also:
Fixed In Version: Current
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-08-22 10:17:10 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
setroubleshooter log (2.29 KB, text/plain)
2007-04-01 18:18 EDT, Andy Burns
no flags Details

  None (edit)
Description Andy Burns 2007-04-01 18:18:34 EDT
Description of problem:


Version-Release number of selected component (if applicable):
F7t3

How reproducible:
not tried yet

Steps to Reproduce:
1. install F7t3 on host
2. attempt to install F7t3 in guest using
3.
  
Actual results:

SELinux prevents networking, guest installation cannot proceed

ERROR: virDomainCreateLinux() failed POST operation failed: (xend.err 'Device 0
(vif) could not be connected. Hotplug scripts not working.')

See attached setroubleshooter log
Comment 1 Andy Burns 2007-04-01 18:18:34 EDT
Created attachment 151396 [details]
setroubleshooter log
Comment 2 Daniel Walsh 2007-04-05 10:40:20 EDT
Fixed in selinux-policy-2.5.11-4.fc7
Comment 3 Matthew Miller 2007-04-10 12:34:15 EDT
Fedora 7 test bugs should be filed against "devel", not against test1/2/3. This
isn't obvious, I know. Moving this report so it isn't lost.

This is a bulk message -- I apologize if this was actually meant to be targeted
against a different release. If so, please fix or let me know. Thanks.
Comment 4 Daniel Walsh 2007-08-22 10:17:10 EDT
Should be fixed in the current release

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