On Fri, Jun 14, 2013 at 11:03:27AM -0400, Matthew Miller wrote: > 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. > > The stuff in the other message aside, there is another thing that can be > problematic. Since systemd starts services in parallel, there's no guarantee > that messages to the console will come in any particular order, or even that > they'll not come at the same time. So, it's possible that the host key > dumped to the console might get another message right in the middle. That's good to know, thank you. I've yet to encounter that, but I'm going to add logic to be not so surprised if the key is missing (with Fedora 18 and, when it's ready, Fedora 19.) FYI. I use the Fedora AMIs for everything AWS. I'm working on packaging the AMIs for Node.js developers to use as a hosting platform, based on my experiences with them: https://github.com/bigeasy/puppy . -- Alan Gutierrez ~ @bigeasy _______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/cloud
