Red Hat Bugzilla – Bug 832765
beta2 3.1 - bridgeless networks are persisted within libvirt on creation
Last modified: 2012-12-04 13:59:52 EST
Description of problem:
Changes to networking via addNetwork/delNetwork/setupNetwork etc must take effect immediately, but should not be persisted until setSafeNetworkConfig is called. This is not the case with bridgeless networks.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. /usr/share/vdsm/addNetwork test '' bond4 eth4 bridged=False
2. restart vdsmd
3. bond4 is broken, but `virsh -r net-list` show vdsm-test.
bridgeless network should not survive restart, just like other networking elements.
as the clientIF comment says:
# this should probably go into vdsm-restore-net script
for network in nets:
if nets[network]['bridged'] and network not in bridges:
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Automated rollback of networking changes in error is not supported in this beta. Manual rebooting of the impacted virtualization hosts, or restoration of their networking configuration, may be required to work around this issue. Working rollback functionality will be provided in a future update.
Verified on vdsm-4.9.6-29.0.el6_3.x86_64
*** Bug 853208 has been marked as a duplicate of this bug. ***
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.