Bug 619687

Summary:	libvirt should not create a bridge on 192.168.122.0 if if already has an IP address on this network
Product:	Red Hat Enterprise Linux 6	Reporter:	Jes Sorensen <Jes.Sorensen>
Component:	libvirt	Assignee:	Daniel Veillard <veillard>
Status:	CLOSED DUPLICATE	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	medium	Docs Contact:
Priority:	low
Version:	6.0	CC:	eblake, jdenemar, xen-maint
Target Milestone:	rc	Keywords:	RHELNAK
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-07-30 10:37:20 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jes Sorensen 2010-07-30 07:21:24 UTC

Description of problem:
Ran into a situation where a RHEL6 guest refused to run yum update. It
showed up that I somehow had gotten libvirt installed in the guest and it
was creating it's dnsmasq bridge on 192.168.122.0 blocking all traffic to
the host network.

Had to chkconfig libvirtd off + reboot to resolve it. ifconfig virbr0 in
the guest did not make the problem go away.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 2 RHEL Program Management 2010-07-30 07:47:44 UTC

This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **

Comment 3 Jiri Denemark 2010-07-30 10:04:08 UTC

What version of libvirt did you installed in the guest? This bug is supposed to be fixed in libvirt-0.8.1-8.el6 (see bug 594494).

Comment 4 Jes Sorensen 2010-07-30 10:10:15 UTC

Hi,

Sorry I didn't record the version that was installed at the time, I
worked around it as described and of course that changed the installed
version. I am pretty sure it was whatever was in beta2, but if you believe
it is fixed in upstream, feel free to close the bug.

Cheers,
Jes

Comment 5 Jes Sorensen 2010-07-30 10:37:20 UTC

Tested the version that was installed with the update: 0.8.1-20 and the
problem is fixed in there.

Comment 6 Jiri Denemark 2010-07-30 10:46:17 UTC


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