Red Hat Bugzilla – Bug 890492
newly defined network is not marked as persistent
Last modified: 2013-01-30 09:39:44 EST
Description of problem: http://libvirt.org/git/?p=libvirt.git;a=commitdiff;h=0211fd6e04cdc402da20818df54299c6ded3d3cb Version-Release number of selected component (if applicable): libvirt-1.0.1 How reproducible: 100% Steps to Reproduce: net = conn.networkDefineXML(netXml) net.create() print net.isPersistent() # net.destroy() # net.undefine() Actual results: net.isPersistent() is reported as false. Expected results: net.isPersistent() is True Additional info: https://www.redhat.com/archives/libvir-list/2012-December/msg01335.html
See https://www.redhat.com/archives/libvir-list/2012-December/msg01367.html, actually we have more problems than this bug exposes.
I believe this upstream patch fixes the problem: commit bb19491cf5e3b78f2d72bbcbcc06e985d29b7f4b Author: Peter Krempa <pkrempa@redhat.com> Date: Fri Jan 11 11:10:34 2013 +0100 network: bridge: Fix regression when defining persistent networks Commit 0211fd6e04cdc402da20818df54299c6ded3d3cb introduced regression where newly defined networks were not made persistent. This patch makes the network persistent on each successful definition.
New libvirt release is scheduled for end of the month and it will promptly end up in rawhide, so just closing this as UPSTREAM
Would you please fill in the "Fixed In Version:" field, so we can require the package when it is ready?
Sorry I didn't realize you guys actually have process around Fedora bugs. I'll reopen and close it when the build actually goes out.
Fixed in libvirt-1.0.1-6.fc19