Comment 10 for bug 1718216

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).