Ubuntu
network-manager package

NetworkManager takes over already used nfsroot interface

Bug #92338 reported by Johannes Frank
6
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Fix Released
Wishlist
Unassigned

Bug Description

Binary package hint: network-manager

On PXE booted enviroments eth0 or equivalent has to be taken out on /etc/network/interfaces in order not to be reconfigured.
But network-manager takes over this interface and thus renders the system unusable.
There is no obvious way to exclude the interface from network-manager, either not being there or not documented in the man-page.
In short: There shout be a /etc/NetworkManager/<excluded-interfaces.conf> for the user to exclude an interface from network-manager, or a clear documentation on how to do this.
The behavior was detected on feisty.

Revision history for this message
Henrik Nilsen Omma (henrik) wrote :

Hi, could you please test this in Gutsy? Network-manager has changes considerably over these releases. We'll only be able to address most bugs in the latest release. Thanks.

Changed in network-manager:
importance: Undecided → Wishlist
status: New → Incomplete
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

This bug report is being closed because we received no reponse to the last inquiry for information. Please reopen it if this is still an issue in the current Gutsy Gibbon release. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Please don't hesitate to submit bug reports in the future, we really appreciate it. Thanks again!

Changed in network-manager:
status: Incomplete → Invalid
Revision history for this message
Henrik Riomar (henrik-riomar) wrote :

This bug is still present in Gutsy.

I added the following code:
   # Check if the root file system is non local (e.g. nfs), exit if it is.
   [ `df -l / | wc -l` -eq 1 ] && exit 0
quite early in /etc/dbus-1/event.d/25NetworkManager & /etc/dbus-1/event.d/26NetworkManagerDispatcher to fix it.

Changed in network-manager:
status: Invalid → New
Revision history for this message
Peter Cordes (peter-cordes) wrote :

casper in Hardy (and maybe earlier) writes a /etc/network/interfaces with
auto eth0
iface eth0 inet manual

 for each interface. This keeps N-M from touching it. Except in Intrepid; see bug 268005 which is a dupe of this bug, since I didn't see this before reporting it.

scripts/nfs doesn't rewrite interfaces, of course, since you can edit it yourself on the NFS server.

Revision history for this message
Alexander Sack (asac) wrote :

since gutsy we dont manage interfaces configure in /etc/network/interfaces anymore. ifupdown and network-manager are mutually exclusive. So given that nfsroot uses something in /etc/network/interfaces, all should be fine for you.

Changed in network-manager:
status: New → Fix Released
Revision history for this message
Peter Cordes (peter-cordes) wrote :

 On more careful reading of this bug (#92338), it seems to be reporting the problem that your main network interface can't be in /etc/network/interfaces if you want to boot with nfsroot. The fix for that is support for the "manual" setting in interfaces(5) to stop ifupdown breaking the nfsroot. e.g.
auto eth0
iface eth0 inet manual

 So I was wrong earlier, and this isn't a dupe of bug 268005, even though they basically cause the same problem. I had been going to send email asking why you closed this even though it was still a problem. But as I discovered, this bug is fixed, and the regression in n-m in Intrepid is a different problem.

 I'm pretty sure bug 268005 will be a problem for nfsroot in general, not just boot=casper. It prevents nfsroot netbooting the Ubuntu Intrepid alpha6 live cd (except with a workaround hack).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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