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:
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):
vdsm-4.9.6-16

How reproducible:


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.
  
Expected results:
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:
                configNetwork.removeLibvirtNetwork(network)

    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.
    
    New Contents:
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.

http://gerrit.ovirt.org/#/c/6991/

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.

http://rhn.redhat.com/errata/RHSA-2012-1508.html