group.of.nepali.translators team mailing list archive
-
group.of.nepali.translators team
-
Mailing list archive
-
Message #16597
[Bug 1693582] Re: cloud-init uses a deprecated metadata path for GCE instance SSH keys
This bug is believed to be fixed in cloud-init in 17.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1693582
Title:
cloud-init uses a deprecated metadata path for GCE instance SSH keys
Status in cloud-init:
Fix Released
Status in cloud-init package in Ubuntu:
Fix Released
Status in cloud-init source package in Xenial:
Fix Released
Status in cloud-init source package in Yakkety:
Fix Released
Status in cloud-init source package in Zesty:
Fix Released
Bug description:
=== Begin SRU Template ===
[Impact]
This code path is only exercised on GCE datasources and in such cases get_data
would have not configured GCE-configured authorized ssh keys for the default user.
[Test Case]
Launch an instance on GCE
Update cloud-init deb
run sudo cloud-init single -n cc_ntp
curl -H "Metadata-Flavor: Google" http://metadata.google.internal/computeMetadata/v1/instance/attributes/ssh-keys
validate .ssh/authorized_keys contains keys listed in the above curl
[Regression Potential]
GCE instances which don't support instance/attributes/ssh-keys would only be able
to configure ssh access via #cloud-config ssh declarations.
[Other Info]
Upstream commit:
https://git.launchpad.net/cloud-init/commit/?id=d27c49391df343d25bd2e24045d2be6bf39c30d2
GCE metadata docs:
https://cloud.google.com/compute/docs/storing-retrieving-metadata
=== End SRU Template ===
~
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1693582/+subscriptions