On Fri, Jun 14, 2013 at 09:34:03AM -0400, Alan Gutierrez wrote: > When I launch the new i386 Fedora 19 image at AWS US East, I don't see the > ssh server public keys nor their fingerprints. I have a bootstrap script > that builds an image based on this image that obtains the public key from > an API call that retrieves the console. No key and the script breaks. > Is this intended or is it an oversight? It is actually neither of those, but a third possibility -- a problem we know about and are working on fixing. :) Or rather, two problems: 1. SELinux policy is blocking cloud-init from setting the hostname, resulting in a one minute delay in booting: https://bugzilla.redhat.com/show_bug.cgi?id=964006 2. cloud-init totally choking on the serial port settings we added to support OpenStack; that port isn't there in EC2 and cloud-init fails to even run: https://bugzilla.redhat.com/show_bug.cgi?id=974285 As soon as we do have EC2 F19 test images that work, we'll post about them right away. And if you have any further insight into these bugs or would like to help test, awesome. -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ <mattdm@xxxxxxxxxxxxxxxxx> _______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/cloud
