can't access sources...

[B Stone Quillin]

1. Google Cloud. Was imported from digitalocean and worked fine until upgraded from 16 to 18

[Scott Moser (smoser)]

Hi,

From the collected 'ds-identify.log' file:

   /etc/cloud/cloud.cfg.d/99-digitalocean.cfg set datasource_list: [ ConfigDrive, DigitalOcean, NoCloud, None ]

So what happened here was that digital ocean put files in their image that limited which DataSources (cloud platforms) cloud-init would search for to the list above. When you moved the system to GCE, then cloud-init did not find a datasource, and the systemd generator in cloud-init disabled cloud-init entirely.

Also, it seems though that something else has explicitly turned on cloud-init. It ran despite the generator not enabling it. I'm not sure what caused that effect.

So... the things that you should do to are to remove /etc/cloud/cloud.cfg.d/99-digitalocean.cfg.

I started some notes at https://hackmd.io/gPKZTbpUTBiBJ_zf7XavbA on things that I noticed changed in the digitalocean image versus the stock ubuntu cloud-images.

[Scott Moser (smoser)]

There is not really anything more I can do on this bug. Essentially it is fallout of a decision made by digitalocean to configure cloud-init in a certain way that limited your ability to move that image to GCE or another cloud platform.

I do not mean to imply that Digital Ocean's change was ill-intentioned. The change may well have been needed in the past but should not be needed now and causes negative side effects as the one that you hit.

I have nothing else to do here but close this bug as 'Invalid'.

If you think otherwise, please feel free to respond.

Scott

[B Stone Quillin (stone4kirby)]

I can completely understand your conclusions. Just one note, after using
GCP to migrate my VM, it worked fine. But after I upgraded to 18.4, then I
got the bug and broke it. Thank you so much for your time and quick reply.

On Fri, Aug 31, 2018, 9:11 AM Scott Moser <email address hidden> wrote:

> There is not really anything more I can do on this bug. Essentially it
> is fallout of a decision made by digitalocean to configure cloud-init in
> a certain way that limited your ability to move that image to GCE or
> another cloud platform.
>
> I do not mean to imply that Digital Ocean's change was ill-intentioned.
> The change may well have been needed in the past but should not be
> needed now and causes negative side effects as the one that you hit.
>
> I have nothing else to do here but close this bug as 'Invalid'.
>
> If you think otherwise, please feel free to respond.
>
> Scott
>
> ** Changed in: cloud-init
> Status: New => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1790092
>
> Title:
> can't access sources...
>
> Status in cloud-init:
> Invalid
>
> Bug description:
> 1. Google Cloud. Was imported from digitalocean and worked fine until
> upgraded from 16 to 18
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/cloud-init/+bug/1790092/+subscriptions
>

[James Falcon (falcojr)]

Tracked in Github Issues as https://github.com/canonical/cloud-init/issues/3230