This seems sane, my one concern is when the device attached with 'iscsistart -b' ends up being the root device. In the other iscsi path (iscsi_target_name=.... iscsi_target_ip=... iscsi_target_port=... and 'ip=..') the 'ip' command writes the configured network information into /run/net-eth0.conf and then open-iscis's initramfs script writes 'eth0' to /run/initramfs/open-iscsi.interface . That instructs open-iscsi's "net-interface-handler" to fake the configuring of 'eth0' without bringing it down.
So, in the iscsistart -N path we need some way to convince ifup that the interface is up. If the interface up code thinks it fails to bring the network up (because its already up, or possibly even had different config), then the network-online.target (static-networking-up in trusty) might not fire, causing things that depend on it to not run. Second thing I'm not sure of, is how interface names are kept consistent between initramfs and post-initramfs. Ie, if iscsistart -N brings up the interface 'eth0', but /etc/network/interfaces and udev rules have set that to be named 'eth1', I'm not what would happen. Third thing, is if there was any networking needed beyond the things that iscsistart could configure (vlan or bonding or additional routes in the configured system for that interface) then I'm not sure if they'd get applied. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1513254 Title: iscsi_auto flag should use iscsistart -N in addition to -b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1513254/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
