Red Hat Bugzilla – Bug 1254611
moving a bridge from a manually-editted eth0 to eth1 keeps eth0 and creates a loop
Last modified: 2016-02-10 14:16:20 EST
Description of problem: vdsm doesn't check if rhevm bridge already exist and creates bridge loop which leads network infrastructure to be flooded. Version-Release number of selected component (if applicable): vdsm-4.16.20-1.el6ev.x86_64 in RHELH based env How reproducible: Unknown. User reported Steps to Reproduce: *Haven't verified* 1. Install rhel, configure bridge named rhevm with out underlying interface (eth0) 2. Attach host to manager. Configure manager to assign rhevm to eth0. Don't touch eth0 Actual results: rhevm bridge created and both eth0 and eth1 are in the bridge Expected results: eth0 removed from the bridge Additional info:
Created attachment 1064325 [details] supervdsm.log
Why did the customer create rhevm bridge to begin with, and why did they move it to another nic? I would not want Vdsm to be over-protective and forcibly remove interfaces the where configured by the local admin. I don't believe that the severity of the issue is urgent, in any case: it can be easily avoided by pre-creating rhevm on top of eth1.
I don't see how I can keep this bug open. In my opinion, whomever edited eth0 manually, should take it down, and edit eth1 manually on the production network. Please reopen if you understand how RHEV can assist the customer in this use case.