group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1628306@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package initramfs-tools - 0.125ubuntu5

---------------
initramfs-tools (0.125ubuntu5) yakkety; urgency=medium

  * scripts/functions: make sure we can try to start all available and suitable
    interfaces if ip= isn't set when setting up the network, and exit as soon
    as we get an IP address. This retains the old behavior from ipconfig when
    ip= is unset, for really simple remote-root scenarios. (LP: #1628306)

 -- Mathieu Trudel-Lapierre <cyphermox@xxxxxxxxxx>  Tue, 27 Sep 2016
18:25:50 -0400

** Changed in: initramfs-tools (Ubuntu Yakkety)
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1628306

Title:
  network booting fails for iscsi root if no ip is set

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  Remote-root installs (eg. / over iscsi and similar) where the configuration is simple, and no extra parameters are included on the kernel command-line (as opposed to MaaS specifying everything).

  [Test case]
  1) do an installation with /boot on a local disk and / and swap over a remote LUN (iSCSI is simple to do).
  2) Update to initramfs-tools with isc-dhcp support.

  [Regression potential]
  This is in itself a fix for a regression found in initramfs-tools (0.125ubuntu4 on yakkety, or 0.122ubuntu8.2 on xenial). Failure to boot on a remote root filesystem would constitue a regression.

  --

  I did a new install with /boot on /dev/sda, and everything else (/ and
  swap) on an iSCSI LUN.

  Booting this with initramfs-tools using ipconfig works without issues.

  Booting this with initramfs-tools (0.125ubuntu4 on yakkety, or
  0.122ubuntu8.2 on xenial) fails because no interface is specified.

  This appears to be because ipconfig interprets "" as meaning to try
  every interface until one works (or all fail), whereas calling
  dhclient without an interface name simply returns a failure.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1628306/+subscriptions