What helped us was simply rebooting the node using PXE (the node should be in allocated state). The node in ready state ends up shut down. So basically what juju does is sending a wake-on-lan signal to start it. If you (like us) powered the node up in ready state, you end up with this particular problem. I hope it doen't matter we hacked the images a little so we could ssh to them to see what's going on and imported ssh keys manually... it shouldn't...
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1015207 Title: juju setup fails, ERROR Invalid SSH key - 12.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1015207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
