Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
The transient network will be vanished after libvirtd restart.
Version-Release number of selected component (if applicable):
libvirt-0.10.2-18.el6_4.3.x86_64
How reproducible:
100%
Steps to Reproduce:
1.
# cat network.xml
<network>
<name>definebr1</name>
<forward/>
<bridge name='definebr1' stp='on' forwardDelay='0' />
<ip address='10.0.0.1' netmask='255.255.255.0'>
<dhcp>
<range start='10.0.0.2' end='10.0.0.254' />
</dhcp>
</ip>
</network>
2.
# virsh net-create network.xml
Network definebr1 created from network.xml
3.
# virsh net-list --all
Name State Autostart Persistent
--------------------------------------------------
default active yes yes
definebr1 active no no
4.
# service libvirtd restart
Stopping libvirtd daemon: [ OK ]
Starting libvirtd daemon: [ OK ]
5.
# virsh net-list --all
Name State Autostart Persistent
--------------------------------------------------
default active yes yes
6.
# brctl show
bridge name bridge id STP enabled interfaces
definebr1 8000.5254000469bb yes definebr1-nic
virbr0 8000.525400a33905 yes virbr0-nic
vnet0
7.
# virsh net-create network.xml
error: Failed to create network from network.xml
error: internal error Network is already in use by interface definebr1
Actual results:
The transient network will be vanished after libvirtd restart.
Expected results:
The transient network still work after libvirtd restart.
Additional info:
As of v1.0.4-215-g446dd66, libvirtd doesn't forget transient networks when restarted.
commit 446dd66b7c7641974d25423c4cb5c48e481a84e4
Author: Peter Krempa <pkrempa>
Date: Tue Apr 16 18:35:59 2013 +0200
network: bridge_driver: don't lose transient networks on daemon restart
Until now tranisent networks weren't really useful as libvirtd wasn't
able to remember them across restarts. This patch adds support for
loading status files of transient networks (that already were generated)
so that the status isn't lost.
This patch chops up virNetworkObjUpdateParseFile and turns it into
virNetworkLoadState and a few friends that will help us to load status
XMLs and refactors the functions that are loading the configs to use
them.
Comment 8RHEL Program Management
2014-04-04 20:58:08 UTC
Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.