Description of problem: One of the supported use cases of vdsm networking is to have an interface (nic or bond) that supports a variety of vlanned networks on top of it. To do so, each vlanned network is added after another over the interface. This can be done in a single operation (which does not expose the bug) of setupNetworks, or it can happen over time. In the latter scenario, if I add a vlanned network now and start using it for services, the current behavior of taking down the vlanned network underlying interface before taking it up again will cause an interruption of the previously configured network. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. Create a vlanned network over a bond. 2. Create a second vlanned network over the same bond. Actual results: You can see in the logs that the bond is taken down and up in step two. Expected results: Since the bond configuration passed in step 2 is the same as in the existing bond set up in step 1, we should not take the bond down, just create the vlan over it. Additional info:
There is an upstream patch under review that is working towards solving the issue: http://gerrit.ovirt.org/#/c/16474/
Added work in progress patch to track it.
rhevm-3.3.0-0.18.master.el6ev.noarch vdsm-4.12.0-92.gita04386d.el6ev.x86_64
This bug is currently attached to errata RHBA-2013:15291. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance.
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/RHBA-2014-0040.html