This bug was fixed in the package cloud-init -
17.2-20-g32a6a176-0ubuntu1
---------------
cloud-init (17.2-20-g32a6a176-0ubuntu1) bionic; urgency=medium
* New upstream snapshot.
- tests: Fix EC2 Platform to return console output as bytes.
- tests: Fix attempted use of /run in a test case.
- GCE: Improvements and changes to ssh key behavior for default user.
[Max Illfelder] (LP: #1670456, #1707033, #1707037, #1707039)
- subp: make ProcessExecutionError have expected types in stderr, stdout.
- tests: when querying ntp server, do not do dns resolution.
- Recognize uppercase vfat disk labels [James Penick] (LP: #1598783)
- tests: remove zesty as supported OS to test
-- Chad Smith <chad.sm...@canonical.com> Tue, 23 Jan 2018 20:10:44
-0700
** Changed in: cloud-init (Ubuntu)
Status: Fix Committed => Fix Released
--
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/1707039
Title:
GCE data source should disregard expired SSH keys
Status in cloud-init:
Fix Committed
Status in cloud-init package in Ubuntu:
Fix Released
Bug description:
GCE supports the expiration of SSH keys. It does so by including the
expiry time in a JSON blob in the comment section of the SSH key. As
per [0], the format is:
ssh-rsa [KEY_VALUE] google-ssh
{"userName":"[USERNAME]","expireOn":"[EXPIRE_TIME]"}
Keys can remain in metadata after expiry, so cloud-init should know
how to filter them out itself.
[0] https://cloud.google.com/compute/docs/instances/adding-removing-ssh-keys
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1707039/+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
