Bug 430741

Summary: Defining a virtual network with an in-use UUID creates a new virtual network
Product: [Fedora] Fedora Reporter: Kaitlin Rupert <kaitlin>
Component: libvirtAssignee: Daniel Veillard <veillard>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: 8CC: berrange
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-01-09 00:52:38 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Kaitlin Rupert 2008-01-29 12:43:55 EST
Description of problem:

Defining a virtual network with an in-use UUID creates a new virtual network, as
well as updating the network with the matching UUID.

Version-Release number of selected component (if applicable): libvirt-0.3.3-2.fc8

How reproducible:
Easy to reproduce.

Steps to Reproduce:
1. sudo virsh net-dumpxml default > net-test.xml
2. vi net-test.xml   <-- edit virtual network name and virtual bridge name
3. sudo virsh net-create net-test.xml 
4. sudo virsh net-list --all
Name                 State      Autostart 
default              active     no        
net-test             active     no    
5. sudo virsh net-dumpxml default
  <bridge name='testbr' stp='on' forwardDelay='0' />
  <ip address='' netmask=''>
      <range start='' end='' />
6. sudo virsh net-destroy net-test
7. sudo virsh net-list --all
Name                 State      Autostart 
default              active     no 
8. sudo virsh net-dumpxml default
  <bridge name='virbr0' stp='on' forwardDelay='0' />
  <ip address='' netmask=''>
      <range start='' end='' />

Actual results:
The networking with the matching UUID (default in this case), is updated
properly.  However, net-list shows both network.  Destroying the new network
removes it from the list, and default reverts back to its original xml.

Expected results:
The default network should have been updated to reflect the changes in the XML.
 A second network should not have been created.

Additional info:
Comment 1 Bug Zapper 2008-11-26 04:37:30 EST
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 8 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 2 Bug Zapper 2009-01-09 00:52:38 EST
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.