Bug 1142864
| Summary: | nmtui cannot change bond mode from active-backup to round-robin | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Dan Williams <dcbw> | ||||||||
| Component: | NetworkManager | Assignee: | Dan Winship <danw> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 7.1 | CC: | danw, dcbw, jklimes, lrintel, thaller, vbenes, vhumpa | ||||||||
| Target Milestone: | rc | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | NetworkManager-0.9.9.1-46.git20140326.4dba720.el7 | Doc Type: | Bug Fix | ||||||||
| Doc Text: |
* Switching a network bond connection from "active-backup" mode to a different mode using the nmtui client failed to remove the interface option, creating an erroneous configuration that would be refused by the NetworkManager daemon. This update fixes the issue. (BZ#1142864)
|
Story Points: | --- | ||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2015-03-05 13:53:17 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
Dan Williams
2014-09-17 14:22:54 UTC
Created attachment 939195 [details] Suggested fix (el7) Please review. el7: (attached) master: https://github.com/lkundrak/NetworkManager/commit/d75103375af79e71125fa312fd461358662d5fe2 > Just drop is as we disable the widget in UI.
typo ("drop is")
I think you need to add the option back in the TRUE case as well; otherwise if you fill in a primary value, then change the mode and then change it back, the entry would still show the old value, but it wouldn't be set in the NMSettingBond.
Does this look better? https://github.com/lkundrak/NetworkManager/commit/fd33ce5a5158b0fbce3d03959393274db7b4223d yes, that looks right Looks right to me too. We may need to do this with other options too, but this fixes the immediate bug. The patch looks good to me. Committed upstream: a36a3a9 tui/bond: remove primary option if mode is not active-backup (rh #1142864) We probably want to include these commits too: 2f36955 tui: fix displaying bond ARP IP targets b0b51ec tui: don't call g_strv_length() on NULL Created attachment 940084 [details] [PATCH] tui: additional fix for 'primary' option Additional fix for primary option. Note: Commits form comment #9 are already contained in NetworkManager-0.9.9.1-40.git20140326.4dba720.el7 (In reply to Jirka Klimes from comment #11) > Created attachment 940084 [details] > [PATCH] tui: additional fix for 'primary' option > > Additional fix for primary option. > > Note: > Commits form comment #9 are already contained in > NetworkManager-0.9.9.1-40.git20140326.4dba720.el7 Yeah, good catch. (In reply to Dan Williams from comment #12) > (In reply to Jirka Klimes from comment #11) > > Created attachment 940084 [details] > > [PATCH] tui: additional fix for 'primary' option > > > > Additional fix for primary option. > > > > Note: > > Commits form comment #9 are already contained in > > NetworkManager-0.9.9.1-40.git20140326.4dba720.el7 > > Yeah, good catch. Upstream: 37f1208 tui: additional fix for 'primary' option Pushed to RHEL 7.1 too: NetworkManager-0.9.9.1-41.git20140326.4dba720.el7 Looks like the 'Primary' option is mandatory for the whole form not depending just on Active Backup mode where it's visible. So it currently blocks the 'OK' trying to create a connection with any other mode. (NetworkManager-0.9.9.1-41) Created attachment 945535 [details]
Revert
I've pushed incomplete fix to el7. This needs to be removed and replaced with a complete fix.
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. https://rhn.redhat.com/errata/RHBA-2015-0311.html |