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.
Previously, when you had more than one VLAN MTU networks attached to a NIC or bond and one network had a higher MTU setting than the other, removing the network with the higher MTU should have caused the MTU on the network or bond to change to reflect the MTU setting of the network with the next-highest MTU setting. This did not happen. VDSM has been updated so that the MTU is updated to reflect the network with the highest MTU setting remaining on the bond or network when the network with the previously-highest network is removed.
Created attachment 610245[details]
vdsm.log
Description of problem:
I have two VLAN MTU networks attached to nic/BOND one with MTU 5000 and one with MTU 9000 the MTU on the nic/BOND is 9000 as is should be.
When removing the network with the highest MTU (9000) the MTU on the nic/BOND is still 9000
Version-Release number of selected component (if applicable):
vdsm-4.9.6-32.0.el6_3.x86_64
How reproducible:
100%
Steps to Reproduce:
1.Create two networks: NONVM_VLAN_MTU_5000 and NONVM_VLAN_MTU_9000
2.attach the networks to nic (ETH0) and apply
3.Remove the network with MTU 9000 (NONVM_VLAN_MTU_9000)
Actual results:
ETH0 still have MTU=9000 in the ifcfg-eth0 file
Expected results:
ETH0 should have MTU=5000 in the ifcfg-eth0 file
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
Created attachment 610245 [details] vdsm.log Description of problem: I have two VLAN MTU networks attached to nic/BOND one with MTU 5000 and one with MTU 9000 the MTU on the nic/BOND is 9000 as is should be. When removing the network with the highest MTU (9000) the MTU on the nic/BOND is still 9000 Version-Release number of selected component (if applicable): vdsm-4.9.6-32.0.el6_3.x86_64 How reproducible: 100% Steps to Reproduce: 1.Create two networks: NONVM_VLAN_MTU_5000 and NONVM_VLAN_MTU_9000 2.attach the networks to nic (ETH0) and apply 3.Remove the network with MTU 9000 (NONVM_VLAN_MTU_9000) Actual results: ETH0 still have MTU=9000 in the ifcfg-eth0 file Expected results: ETH0 should have MTU=5000 in the ifcfg-eth0 file