Created attachment 524175[details]
network scripts
Description of problem:
Configure nic bonding with two nics using mode 4, after register to rhevm, one of the bonding nics goes down after register to rhevm, the content of network scripts are changed, also the content of /proc/net/bonding/bond4.
Version-Release number of selected component (if applicable):
vdsm-4.9-96.1.el6.x86_64
rhev-hypervisor-6.2-0.17.2
rhevm 140.2
How reproducible:
Always.
Steps to reproduce:
1. Configure nic bonding with two nics using mode 4.
2. Register to rhevm.
3. Drop to shell, run ifconfig to check the network.
Actual results:
one of the bonding nics goes down after register to rhevm, the content of network scripts are changed, also the content of /proc/net/bonding/bond4.
Expected results:
it should only change the bridge's name to rhevm, others should keep the same before register to rhevm.
Additional info:
Please refer to attachment for the network scripts before and after register to rhevm.
This seems like a dup of bug 531390. Am I correct?
You can circumvent that issue by pre-defining a bridge called rhevm and connecting it to your bonding device.
(In reply to comment #2)
> This seems like a dup of bug 531390. Am I correct?
>
> You can circumvent that issue by pre-defining a bridge called rhevm and
> connecting it to your bonding device.
pre-defining a bridge called rhevm over bonding device did not meet this issue, register to rhevm, all network device's scripts keep the same.
Created attachment 524175 [details] network scripts Description of problem: Configure nic bonding with two nics using mode 4, after register to rhevm, one of the bonding nics goes down after register to rhevm, the content of network scripts are changed, also the content of /proc/net/bonding/bond4. Version-Release number of selected component (if applicable): vdsm-4.9-96.1.el6.x86_64 rhev-hypervisor-6.2-0.17.2 rhevm 140.2 How reproducible: Always. Steps to reproduce: 1. Configure nic bonding with two nics using mode 4. 2. Register to rhevm. 3. Drop to shell, run ifconfig to check the network. Actual results: one of the bonding nics goes down after register to rhevm, the content of network scripts are changed, also the content of /proc/net/bonding/bond4. Expected results: it should only change the bridge's name to rhevm, others should keep the same before register to rhevm. Additional info: Please refer to attachment for the network scripts before and after register to rhevm.