net-interface-handler needs updating for newer ifupdown
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
open-iscsi (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
newer ifupdown versions (those in xenial) now keep interface state in /run/network/
We need to update /lib/open-
The failure can be seen when booting a maas image, if you first move the included symlink out of the way:
p="/etc/
[ -e "$p.link" -o -L "$p.link" ] || mv "$p" "$p.link"; cp "$p.dist" "$p"
(maas images ship with /etc/network/
and /run/network/
This affects:
* cloud-init: cloud-init's fallback config currently writes 'auto' for the network device. the cloud-initramfs
* maas-images: the single difference from filesystem viewpoint from xenial lxd image to maas image is 'ln -snf ../../run/
* open-iscsi: the real need for open-iscsi's udev integration is to get the resolvconf updates applied.
Related bugs:
* bug 1568637: network config of initramfs devices writes 'auto', breaking iscsi root boot
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: open-iscsi 2.0.873+
ProcVersionSign
Uname: Linux 4.4.0-18-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
Date: Wed Apr 13 23:58:27 2016
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
SourcePackage: open-iscsi
UpgradeStatus: No upgrade log present (probably fresh install)
tags: | added: patch |
Changed in cloud-init: | |
status: | New → Confirmed |
Changed in maas-images: | |
status: | New → Confirmed |
Changed in cloud-init (Ubuntu): | |
status: | New → Confirmed |
description: | updated |
no longer affects: | cloud-init (Ubuntu) |
no longer affects: | maas-images |
no longer affects: | cloud-init |
description: | updated |
At this point, I think the second patch there is doing the right thing. -dyn-netconf is writing 'manual eth0'. cloud-init's version means that ifupdown tries to bring the device down on shutdown.
The reason I asked slangasek to NAC my upload was that poweroff wasnt' working correctly.
The reason poweroff wasn't working correctly was that cloud-init is writing 'auto eth0' where cloud-initramfs