Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
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.