On Fri, Mar 15, 2019 at 2:50 PM Rod Smith <email address hidden> wrote:
> Thanks for the quick fix, Ryan! I've confirmed that your curtin config
> workaround in comment #15 works. Do you have an estimate for how long
> it'll be before a fix goes live? (I ask so we can plan whether we should
> push your workaround through one of the certification packages.)
>
Depends on where you need it. It can likely land upstream either today
or on Monday; and would be available via the cloud-init-dev daily PPA;
however, an SRU will take at least another week after next; We're almost
done with an existing cloud-init SRU; so we'd likely not start another SRU
until the current one is in -updates.
On Fri, Mar 15, 2019 at 2:50 PM Rod Smith <email address hidden> wrote:
> Thanks for the quick fix, Ryan! I've confirmed that your curtin config
> workaround in comment #15 works. Do you have an estimate for how long
> it'll be before a fix goes live? (I ask so we can plan whether we should
> push your workaround through one of the certification packages.)
>
Depends on where you need it. It can likely land upstream either today
or on Monday; and would be available via the cloud-init-dev daily PPA;
however, an SRU will take at least another week after next; We're almost
done with an existing cloud-init SRU; so we'd likely not start another SRU
until the current one is in -updates.
> /bugs.launchpad .net/bugs/ 1819994 /bugs.launchpad .net/cloud- init/+bug/ 1819994/ +subscriptions
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> cloud-init selects sysconfig netconfig renderer if network-manager is
> installed on Ubuntu
>
> To manage notifications about this bug go to:
> https:/
>