yahoo-eng-team team mailing list archive

[Scott Moser <ssmoser2+ubuntu@xxxxxxxxx>]

This bug is believed to be fixed in cloud-init in 18.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 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 Released
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