| Thread Previous • Date Previous • Date Next • Thread Next |
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 a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
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
| Thread Previous • Date Previous • Date Next • Thread Next |
