Comment 5 for bug 1714028

On Tue, Oct 3, 2017 at 9:48 AM, Dimitri John Ledkov <email address hidden>
wrote:

> Image 8-30 had re-introduced ifupdown due to $reasons. Thus any image
> before or after would have been better.
>

We are currently still failing in maas images:

artful amd64/hwe-a 20170928 root-image.gz

> Current daily images do not have neither ifupdown or resolvconf on them.
>
> Are there specific netplan/networkd/resolved bugs i should look into
> trianging/debugging/fixing to have a working curtin for artful release?
>

Can you confirm when we will have an artful maas image with no ifupdown?
We'll likely see it when it's there at our daily vmtests:

https://jenkins.ubuntu.com/server/view/curtin/job/curtin-vmtest-devel-amd64/

The current image (9/28) still has ifupdown in it.

> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1714028
>
> Title:
> artful network vmtests fail now that resovlconf is missing (and
> ifupdown is still present)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/curtin/+bug/1714028/+subscriptions
>