artful: failure to setup networking

Bug #1718216 reported by Andreas Hasenack on 2017-09-19
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

maas 2.2.2 (6099-g8751f91-0ubuntu1~16.04.1) on xenial
curtin 0.1.0~bzr505-0ubuntu1~16.04.1

Trying to deploy artful image 20170916 on to a VM with two disks, two nics, each connected to a different network. In MAAS only one nic is configured.

During final boot, networking fails to come up (see attached screenshot for the waiting period). After booting into single user mode and setting a password for the ubuntu user, and logging in at the console as ubuntu, only the "lo" interface is up.

Attached are several log and configuration files.

Related branches

Andreas Hasenack (ahasenack) wrote :

/etc of the node

Andreas Hasenack (ahasenack) wrote :
Andreas Hasenack (ahasenack) wrote :
Andreas Hasenack (ahasenack) wrote :
Andreas Hasenack (ahasenack) wrote :
Andreas Hasenack (ahasenack) wrote :
description: updated
description: updated
Andreas Hasenack (ahasenack) wrote :
Ryan Harper (raharper) wrote :

Hi, curtin 505 will only generate eni which requires functioning ifupdown in the target image.
Artful does not currently utilize ifupdown but netplan+systemd-networkd.

What's happening is that artful attempts to bring networking online, but no interface comes up due to artful image not having ifupdown/networking service which usually brings the network up.

Curtin trunk will detect if the target image cloud-init supports accepting network configuration and if so will pass the mass network config into the image for rendering during boot.

Passing the config to cloud-init is the preferred/long term target for curtin; curtin will need an SRU to bring network-passthrough back to xenial-updates; this was delayed until the most recent cloud-init SRU was complete (which included critical eni rendering fixes which could have regressed network config for some images).

Ryan Harper (raharper) wrote :

You can install curtin trunk from the PPA:

sudo add-apt-repository ppa:curtin-dev/daily

Upgrade to that curtin should allow your artful deploy; networking should come up but DNS is currently broken in artful.

Download full text (11.0 KiB)

For whatever it is worth I wanted to mention - this is working for me on Wichita.
MAAS version: 2.2.2 (6099-g8751f91-0ubuntu1~16.04.1)
Curtin: (0.1.0~bzr526-0ubuntu1~ubuntu16.04.1)

This is a power box, the install log is here:
curtin: Installation started. (0.1.0~bzr526-0ubuntu1~ubuntu16.04.1)
third party drivers not installed or necessary.
Creating new GPT entries.
The operation has completed successfully.
Get:1 artful InRelease [237 kB]
Hit:2 artful-updates InRelease
Get:3 artful-backports InRelease [65.5 kB]
Hit:4 artful-security InRelease
Get:5 artful/universe ppc64el Packages [7793 kB]
Get:6 artful/multiverse ppc64el Packages [131 kB]
Get:7 artful/main ppc64el Packages [1065 kB]
Fetched 9291 kB in 2s (4382 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  crda grub-common grub-ieee1275 grub-ieee1275-bin grub2-common iw libnl-3-200
  libnl-genl-3-200 linux-firmware linux-headers-4.12.0-13
  linux-headers-4.12.0-13-generic linux-headers-generic
  linux-image-4.12.0-13-generic linux-image-extra-4.12.0-13-generic
  linux-image-generic os-prober wireless-regdb
Suggested packages:
  multiboot-doc xorriso desktop-base genisoimage fdutils linux-doc-4.12.0
  | linux-source-4.12.0 linux-tools
The following NEW packages will be installed:
  crda grub-common grub-ieee1275 grub-ieee1275-bin grub2-common iw libnl-3-200
  libnl-genl-3-200 linux-firmware linux-generic linux-headers-4.12.0-13
  linux-headers-4.12.0-13-generic linux-headers-generic
  linux-image-4.12.0-13-generic linux-image-extra-4.12.0-13-generic
  linux-image-generic os-prober wireless-regdb
0 upgraded, 18 newly installed, 0 to remove and 8 not upgraded.
Need to get 104 MB of archives.
After this operation, 586 MB of additional disk space will be used.
Get:1 artful/main ppc64el grub-common ppc64el 2.02~beta3-4ubuntu6 [1638 kB]
Get:2 artful/main ppc64el grub2-common ppc64el 2.02~beta3-4ubuntu6 [514 kB]
Get:3 artful/main ppc64el grub-ieee1275-bin ppc64el 2.02~beta3-4ubuntu6 [533 kB]
Get:4 artful/main ppc64el grub-ieee1275 ppc64el 2.02~beta3-4ubuntu6 [61.1 kB]
Get:5 artful/main ppc64el libnl-3-200 ppc64el 3.2.29-0ubuntu3 [48.8 kB]
Get:6 artful/main ppc64el libnl-genl-3-200 ppc64el 3.2.29-0ubuntu3 [10.8 kB]
Get:7 artful/main ppc64el wireless-regdb all 2016.06.10-0ubuntu1 [8824 B]
Get:8 artful/main ppc64el iw ppc64el 4.9-0.1 [68.3 kB]
Get:9 artful/main ppc64el crda ppc64el 3.18-0ubuntu1 [63.4 kB]
Get:10 artful/main ppc64el linux-firmware all 1.168 [40.9 MB...

Andreas Hasenack (ahasenack) wrote :

> Curtin: (0.1.0~bzr526-0ubuntu1~ubuntu16.04.1)

That comes from the PPA Ryan mentioned, so good to see that it fixes this problem :)

Scott Moser (smoser) on 2017-10-02
Changed in curtin:
status: New → Fix Committed
importance: Undecided → Medium

This bug is believed to be fixed in curtin in 17.1. If this is still a problem for you, please make a comment and set the state back to New

Thank you.

Changed in curtin:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers