[Bug 1556241] Re: installer sets "iface encf5f0 inet dhcp" although a static IP address was preseeded

Steve Langasek steve.langasek at canonical.com
Wed Mar 23 14:11:47 UTC 2016


ubuntu-snappy should not write out its separate network interface config
when installed on an Ubuntu classic system.  mvo asked this to be filed
as a critical bug against ubuntu-snappy.

In general, the ubuntu-snappy firstboot task does not apply to an Ubuntu
classic system.  While it sounds like the Snappy team will take steps to
disable this in the future, as a workaround for new installs, we can
make the installer touch /var/lib/snappy/firstboot/stamp on install.

** Changed in: ubuntu-snappy (Ubuntu)
   Importance: Undecided => Critical

** Changed in: ubuntu-snappy (Ubuntu)
       Status: New => Triaged

** Package changed: snappy (Ubuntu) => debian-installer (Ubuntu)

** Changed in: debian-installer (Ubuntu)
   Importance: Critical => High

** Changed in: debian-installer (Ubuntu)
       Status: Confirmed => Triaged

** Changed in: debian-installer (Ubuntu)
     Assignee: Dimitri John Ledkov (xnox) => Mathieu Trudel-Lapierre (mathieu-tl)

** Changed in: ubuntu-snappy (Ubuntu)
    Milestone: None => ubuntu-16.04

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to debian-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1556241

Title:
  installer sets "iface encf5f0 inet dhcp" although a static IP address
  was preseeded

Status in debian-installer package in Ubuntu:
  Triaged
Status in ubuntu-snappy package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - Thorsten Diehl - 2016-03-11 12:49:44 ==
  I installed xenial with installer version 432 and a preseed file that has a IPv4 static configuration. Upon the initial boot after installation, everything is fine, system comes up with network. When I perform a reboot, the network service waits for "something" and prints continuously messages aka "A start job is running for Raise network interfaces (3min 14s / 5min)". After that, the network is up.
  I found, that it was waiting for DHCP responses. (attaching /var/log/syslog).
  /etc/network/interfaces looks like this:
  # This file describes the network interfaces available on your system
  # and how to activate them. For more information, see interfaces(5).

  source /etc/network/interfaces.d/*

  # The loopback network interface
  auto lo
  iface lo inet loopback

  # The primary network interface
  auto encf5f0
  iface encf5f0 inet static
  	address 9.152.162.158
  	netmask 255.255.252.0
  	network 9.152.160.0
  	broadcast 9.152.163.255
  	gateway 9.152.160.1
  	# dns-* options are implemented by the resolvconf package, if installed
  	dns-nameservers 9.152.120.241
  	dns-search boeblingen.de.ibm.com
  /etc/network/interfaces.d/encf5f0 looks like this:
  allow-hotplug encf5f0
  iface encf5f0 inet dhcp
  which seems to be the cause. After removing the second line, it worked as expected.

  Not sure, whether this is the best approach. I just wanted to point to
  the root cause. But starting a dhcp client when you have a static IP
  address configured is definitely wrong.

  == Comment: #2 - Thorsten Diehl <thorsten.diehl at de.ibm.com> - 2016-03-11 12:55:54 ==
  uname -r
  4.4.0-12-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1556241/+subscriptions



More information about the foundations-bugs mailing list