newer ifupdown versions (those in xenial) now keep interface state in /run/network/ifstate.<interfacename> rather than combined in /run/network/ifstate .
We need to update /lib/open-iscsi/net-interface-handler to write the interface name into /run/network/ifstate.<interfacename> and then also tear that down on down.
The failure can be seen when booting a maas image, if you first move the included symlink out of the way:
p="/etc/network/interfaces";
[ -e "$p.link" -o -L "$p.link" ] || mv "$p" "$p.link"; cp "$p.dist" "$p"
(maas images ship with /etc/network/interfaces as a symlink to ../../run/network/dynamic-interfaces
and /run/network/dynamic-interfaces is populated by cloud-initramfs-dyn-netconf).
This affects:
* cloud-init: cloud-init's fallback config currently writes 'auto' for the network device. the cloud-initramfs-dyn-netconf writes 'manual', and so ifupdown doesn't try to bring up *or* down the device.
* maas-images: the single difference from filesystem viewpoint from xenial lxd image to maas image is 'ln -snf ../../run/dynamic-interfaces /etc/network/interfaces'
* 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+git0.3b4b4500-14ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
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-256color
PATH=(custom, no user)
SourcePackage: open-iscsi
UpgradeStatus: No upgrade log present (probably fresh install)
At this point, I think the second patch there is doing the right thing.
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