[Bug 1077700] Re: Issue with ConfigDriveV2 and ssh authorized_keys

[Scott Moser]

** Description changed:

- cloud-init (latest sources) is not getting the public key from config
- drive. Tested on an Ubuntu 12.04 instance.
+ == SRU Information ==
+ [Impact]
+  * Users of openstack who use config-drive version 2 (added in folsom/quantal) will not have their ssh keys imported from the config drive.  They can use other means (ssh-import-id) to get ssh keys imported, but users would expect instances launched with a given key to have access to the instance with that key.
+  * without this fix images don't work as expected with OpenStack folsom and confdig-drive-v2.
+  * The bug was simply that the cloud-init key was expecting a key named 'public-keys' and openstack named it 'public_keys'
+ 
+ [Test Case]
+  * launch cloud-image instance on openstack folsom or grizzly with config-drive enabled passing, and pass in a ssh key (nova boot --key_name).
+  * attempt to ssh in as 'ubuntu@' and see failure.
+ 
+ [Regression Potential]
+  * low chance for regression.  fix is tested in raring. Potential for regression would really be in a patched OpenStack.
+ 
+ == End SRU Information ==
+ 
+ 
+ cloud-init (latest sources) is not getting the public key from config drive. Tested on an Ubuntu 12.04 instance.
  
  A patch is attached.
  
  Here's the content of the configdrive generated by Nova:
  
  https://dl.dropbox.com/u/9060190/configdrive.tar.gz

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1077700

Title:
  Issue with ConfigDriveV2 and ssh authorized_keys

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1077700/+subscriptions