[karmic regression] Network manager does not unmanage devices configured as "mapping" in /etc/network/interfaces

I just confirmed. Looks like the ifupdown plugin needs some work, although it reads /etc/network/interfaces, it fails to pass along the information. The call SCPluginIfupdown_get_unmanaged_specs() always returns an empty list.

Note my testing was done with an unreleased version: 0.8~a~git.20090812t221559.2e849a0-0ubuntu1

I added:

mapping eth0
    script guessnet-ifupdown
    map default: missing-cable
    map verbose: false
    map debug: false
    map missing-cable work-fixed home-fixed aruba-abi aruba-misc home-fixed2

to /etc/home/interfaces, and tried with NM 0.7.1, and NM 0.8*, the former works correctly ( NM leave eth0 unmanaged ), the latter does not.

It appears this is only a bug if the "mapping" stanzas are used.

Can anyone still reproduce this? I believe that it may have been fixed on September 4 (upstream).

Noel,

I still have the bug:

network-manager:
  Installed: 0.8~a~git.20090930t162132.866d48b-0ubuntu1~nmt1
  Candidate: 0.8~a~git.20090930t162132.866d48b-0ubuntu1~nmt1
  Version table:
 *** 0.8~a~git.20090930t162132.866d48b-0ubuntu1~nmt1 0
        500 http://ppa.launchpad.net karmic/main Packages
        100 /var/lib/dpkg/status
     0.8~a~git.20090923t064445.b20cef2-0ubuntu2 0
        500 http://archive.ubuntu.com karmic/main Packages
network-manager-gnome:
  Installed: 0.8~a~git.20091002t194214.8515a07-0ubuntu1~nmt1
  Candidate: 0.8~a~git.20091002t194214.8515a07-0ubuntu1~nmt1
  Version table:
 *** 0.8~a~git.20091002t194214.8515a07-0ubuntu1~nmt1 0
        500 http://ppa.launchpad.net karmic/main Packages
        100 /var/lib/dpkg/status
     0.8~a~git.20090923t220421.1ac8ffd-0ubuntu4 0
        500 http://archive.ubuntu.com karmic/main Packages

Attached file is my daemon.log with all the relevant data

afaik i committed the mapping stanza support upstream a while back. anyone can confirm that this is fixed in latest builds in karmic?

marking fix released for now. If you still have that problem with latest karmic version, please reopen.

@asac, see comment #6. Shouldn't the assumed code have been in there?

I retested it again, on request of asac.

Attached logfile of command: sudo NetworkManager --no-daemon 2>&1 | tee /tmp/nm.log.txt

If I stop networkmanager after this command it core dumps, leaving info behind in /var/crash. Unable to collect it with ubuntu-bug since it is a package from the PPA.

committed fix upstream: 8b3ddc7c8a83d11c7a9f063028b27650a109abd6

This bug was fixed in the package network-manager - 0.8~a~git.20091005t192303.1d28ad1-0ubuntu1

---------------
network-manager (0.8~a~git.20091005t192303.1d28ad1-0ubuntu1) karmic; urgency=low

  * upstream snapshot 2009-10-05 19:23:03 (GMT)
    + 1d28ad1aa54bacf6b6b64582ee7c41d9728d7304
  * fixed upstream
    - LP: #413622 - Network manager does not unmanage devices configured as
      "mapping" in /etc/network/interfaces
    - LP: #413967 - Network manager does not connect wlan0 on startup
    - LP: #417719 - Disconnected static wired network initially treated as
      connected
    - LP: #422597 - 802.11x fails for wired connections (wireless works)
    - LP: #438771 - Creating a wireless or DSL connection fails with
      "Error editing connection: property '%s' / '%s' invalid: %d"
    - LP: #443423 - Connection properties are not stored
    - LP: #439221 - cannot create wireless Wpa & Wpa2 connection with GUI
    - LP: #441668 - network-manager does not save modifications on GSM
      connections
    - LP: #438454 - NetworkManager fails to set IP and route information entered

  [ Mathieu Trudel <email address hidden> ]
  * updated pkcs11 smartcard patch
    - updated debian/patches/lp120363_smartcard_pkcs11.patch
  * add new 802.1x symbols to libnm-util1.symbols
    - update debian/libnm-util1.symbols

  [ Alexander Sack <email address hidden> ]
  * drop cherry-pick now applied upstream
    - delete debian/patches/lp436884.patch
    - update debian/patches/series
  * extend apport hook to also append /etc/NetworkManager/nm-system-settings.conf
    - update debian/source_network-manager.py

 -- Alexander Sack <email address hidden> Mon, 05 Oct 2009 23:46:01 +0200

remote bug tracker bug doesn't exist according to lp. But it does :)
Setting to manual and closing the remote bug as well (since it is closed at gnome).