ifupdown hides the connections of the keyfile plugin if there are connections managed by ifupdown (not NM)

Bug #663805 reported by Florian Hackenberger
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
NetworkManager
Fix Released
Critical
network-manager (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: network-manager

SRU JUSTIFICATION:

Simple patch to avoid blocking loading all the connections if eth0 is found by the ifupdown plugin (e.g. configured in /etc/network/interfaces), with ifupdown set to unmanaged. Some further connections may need to be loading from the keyfile plugin.

TEST CASES:

---

The ifupdown plugin causes the keyfile plugin to break if there is a connection
managed by ifupdown (/etc/network/interfaces) and the keyfile plugin is loaded
after ifupdown as specified in /etc/NetworkManager/nm-system-settings.conf by
default.

A workaround is to change the order of the plugins and make sure ifupdown is
the last. So change:

plugins=ifupdown,keyfile

to

plugins=keyfile,ifupdown

in /etc/NetworkManager/nm-system-settings.conf

See upstream bug https://bugzilla.gnome.org/show_bug.cgi?id=632675

Revision history for this message
Florian Hackenberger (f-hackenberger) wrote :

It would be great if the workaround could be incorporated into an SRU.

Revision history for this message
Florian Hackenberger (f-hackenberger) wrote :
Changed in network-manager:
importance: Unknown → Critical
status: Unknown → Fix Released
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Florian,

What release was this for (I guess Lucid, but just checking)?

For a possible SRU, I'd instead apply the upstream fix, since it's not very intrusive.

Changed in network-manager (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
tags: added: nm-possible-sru
Revision history for this message
Florian Hackenberger (f-hackenberger) wrote :

Lucid, yes.

Thanks for processing this bugreport!

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Assigning to myself so I can prepare a package to test this fix with.

Changed in network-manager (Ubuntu):
assignee: nobody → Mathieu Trudel-Lapierre (mathieu-tl)
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Florian,

I can happily prepare a package that fixes the issue; but could you please clarify the exact TEST CASES in the description above, so that it's clear for people trying to verify the fix? Thanks!

description: updated
tags: added: testcase
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Test cases need to be clarified as to how exactly to reproduce the bug and verify that it's fixed by a SRU. Marking Incomplete for now (and unassigning myself).

Changed in network-manager (Ubuntu):
status: Triaged → Incomplete
assignee: Mathieu Trudel-Lapierre (mathieu-tl) → nobody
Revision history for this message
Bryan Quigley (bryanquigley) wrote :

This was fixed in upstream long ago so it's likely fixed in Ubuntu too.

Changed in network-manager (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.