** Description changed: === 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 with don't support instance/attributes/ssh-keys would only be able + 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 + https://git.launchpad.net/cloud-init/commit/?id=d27c49391df343d25bd2e24045d2be6bf39c30d2 GCE metadata docs: - https://cloud.google.com/compute/docs/storing-retrieving-metadata + https://cloud.google.com/compute/docs/storing-retrieving-metadata === End SRU Template === ~
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1693582 Title: cloud-init uses a deprecated metadata path for GCE instance SSH keys To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1693582/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
