Bug 1275035
Summary: | NetworkManager Bond MTU Fails to Set | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Trae Santiago <tsantiago> | ||||
Component: | NetworkManager | Assignee: | Rashid Khan <rkhan> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Desktop QE <desktop-qa-list> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 7.1 | CC: | aloughla, bgalvani, dcbw, jklimes, lrintel, rkhan, thaller, trae32566, tsantiago | ||||
Target Milestone: | rc | Keywords: | Reopened | ||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2016-02-02 11:27:00 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Trae Santiago
2015-10-25 07:17:27 UTC
I forgot to mention a somewhat obvious step: 5. Re-initialize the connections: nmcli c up bond0 This has been fixed in bug 1177860 and will be delivered in RHEL 7.2. Upstream commit: http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=nm-1-0&id=5359322b6dcac8cdf7a26464f995f2b097618ca7 and http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=nm-1-0&id=33ee3b2a496133fb532e02838570fdae72f63275 Just a note, if a connection profile is changed, it is not re-applied automatically. It has to be activated manually so that the changes could appear on device, like: $ nmcli con up bond0-slave0 (restarting NetworkManager does it too as long as the profiles has autoconnect property set) Hello, It appears that this is fixed only for new servers (ie: a yum upgrade will not fix the issue). I've tested this both with the server originally exhibiting the issue, and with a new server which was installed using 7.0 media and upgraded to 7.2. Has the issue been verified as fixed on an existing server? Perhaps I'm doing something wrong. Thanks, Trae S. (In reply to Trae Santiago from comment #6) > Hello, > > It appears that this is fixed only for new servers (ie: a yum upgrade will > not fix the issue). I've tested this both with the server originally > exhibiting the issue, and with a new server which was installed using 7.0 > media and upgraded to 7.2. Has the issue been verified as fixed on an > existing server? Perhaps I'm doing something wrong. yum upgrade doesn't restart the NetworkManager service, but I assume you rebooted after the upgrade anyway? I assume you activated the connection anew after modifying the MTU (like `nmcli connection up bond0`)? It's not very likely that NetworkManager behaves differently depending on whether you got the package from a fresh-installation or from an upgrade. What is your NetworkManager version? I found the issue, I apologize. I do have a relevant issue with teaming, basically the same issue regarding MTU, but I should probably open a new bug report for that I'm guessing? Thanks for the quick response! Ok, closing again. yes, please open a new bug. Thank you!! |