Tracked in Github Issues as https://github.com/canonical/cloud- init/issues/3396
** Bug watch added: github.com/canonical/cloud-init/issues #3396 https://github.com/canonical/cloud-init/issues/3396 ** Changed in: cloud-init Status: Triaged => Expired -- 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/1834065 Title: cloud-init v19.1 fails to read user-data if a VM on CloudSigma doesn't have a ssh public key in VM properties/SSH keys Status in cloud-init: Expired Bug description: I'm using python 3 to access CloudSigma resources. There are two python libraries that can be used to access CloudSigma, libcloud and pycloudsigma. Neither have functions to deal with VM instance ssh public keys. There are REST API paths /api/2.0/keypairs/ and /api/2.0/pubkeys/ but they are not in either of the libraries' code) I can't add the ssh_public_key to the VM metadata because it's a reserved word. "! Reserved meta keys are: Description, ssh_public_key, optimize_for." If I try to add it, it just disappears in the web dashboard. The only choice for me seems to be using CloudSigma's web dashboard to attach the ssh public key to the VM instance and that's not what I would like to do. rharper on irc suggested to patch DataSourceCloudSigma.py to change self.ssh_public_key = server_meta['ssh_public_key'] to self.ssh_public_key = server_meta.get('ssh_public_key', '') and it seems to work. I've included the cloud-init collect-logs tar package. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1834065/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
