Comment 2 for bug 1633232

On Thu, Oct 13, 2016 at 7:24 PM, Steve Langasek <
<email address hidden>> wrote:

> We do need to support creating all-snap images that support reading
> cloud init data from a network source. However, this bug report
>

There is more than one way to get a local seed.

ubuntu-image assumes it will embed the nocloud-net seed *inside* the image
versus say attaching a USB or CDROM to the machine on which the user-data
seed is present.

> supposes that this should be the default, i.e. when no --cloud-init
> option is passed. I don't agree that this should be the default -
> preparing a generic image that you want to collect configuration
> information from the network that it's attached to is /not/ the common
> case for snappy, the common case is that the network you're attaching to
> is unknown/untrusted, and doesn't have any data source anyway leading to
> annoying timeouts on boot.
>

There's more than network. additionally, cloud-init is *disabled* by
default unless you create a gadget snap with a 'cloud.conf' file
in it, so the timeout is unrelated to common case.

>
> So allowing cloud-init to search for network data sources should be
> handled with an additional option. I don't know if this option belongs
> on the ubuntu-image commandline, vs. as part of the model assertion.
>
>
This bug isn't strictly about network data sources, rather just not
embedding a seed
unless someone provides some config a built-time.

> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1633232
>
> Title:
> do not create nocloud-net seed without --cloud-init parameter
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu-image/+bug/1633232/+subscriptions
>