Bug 781890

Summary:	default network definition came back from the dead
Product:	[Fedora] Fedora	Reporter:	Tom Horsley <horsley1953>
Component:	libvirt	Assignee:	Laine Stump <laine>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	16	CC:	berrange, clalancette, crobinso, dallan, dougsland, itamar, jforbes, laine, libvirt-maint, veillard, 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-21 02:27:47 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Tom Horsley 2012-01-16 01:27:48 UTC

Description of problem:

I just got a libvirt update, and when I rebooted my system I found the
virbr0 interface had been created and dnsmasq running.

Long ago I removed the default network definition via:

virsh net-destroy default
virsh net-undefine default

Yet now, a libvirt update has apparently brought it back.

Seems like a bug to me that a sysadmin's libvirt configuration
would be changed by an update.

Version-Release number of selected component (if applicable):
libvirt-0.9.6-4.fc16.x86_64

How reproducible:
Just did the update, but I suspect it would happen again.

Steps to Reproduce:
1.see above
2.
3.
  
Actual results:
Default network has apparently returned.

Expected results:
Leave my configuration alone.

Additional info:

Comment 1 Dave Allan 2012-01-16 15:47:12 UTC

This question really needs to be discussed upstream, but I'm starting to think that Fedora should ship a libvirt-config RPM that contains things like the default network so people can avoid having the default network configured if they don't want it.

Comment 2 Cole Robinson 2012-06-07 20:33:57 UTC

We ended up doing that in F17 at least. Maybe worth doing for F16.

Tom, you can actually make it stop by just doing

virsh net-destroy default
virsh net-autostart --disable default

Skipping the undefine step should prevent libvirt from enabling the network.

Comment 3 Cole Robinson 2012-10-21 02:27:47 UTC

I think F17 got this right on upgrade, so just closing as CURRENTRELEASE