Given that this looked like it might just be an ssh key issue (which is certainly a problem -- I wasn't able to ssh to the member servers as the ubuntu user) I set a password in maas.preseed and added keys to authorized_keys post-installation. That fixed the initial key problem but juju seems to not be able to communicate with these servers:
root@maas01:~# juju -v status 2012-06-25 15:04:57,585 DEBUG Initializing juju status runtime 2012-06-25 15:04:57,593 INFO Connecting to environment... 2012-06-25 15:04:57,715 DEBUG Connecting to environment using server02.blah.com... 2012-06-25 15:04:57,715 DEBUG Spawning SSH process with remote_user="ubuntu" remote_host="server02.blah.com" remote_port="2181" local_port="39073". 2012-06-25 15:04:58,220:11766(0x7fbdcbf5d700):ZOO_INFO@log_env@658: Client environment:zookeeper.version=zookeeper C client 3.3.5 2012-06-25 15:04:58,220:11766(0x7fbdcbf5d700):ZOO_INFO@log_env@662: Client environment:host.name=maas01 2012-06-25 15:04:58,220:11766(0x7fbdcbf5d700):ZOO_INFO@log_env@669: Client environment:os.name=Linux 2012-06-25 15:04:58,220:11766(0x7fbdcbf5d700):ZOO_INFO@log_env@670: Client environment:os.arch=3.2.0-25-generic 2012-06-25 15:04:58,220:11766(0x7fbdcbf5d700):ZOO_INFO@log_env@671: Client environment:os.version=#40-Ubuntu SMP Wed May 23 20:30:51 UTC 2012 2012-06-25 15:04:58,221:11766(0x7fbdcbf5d700):ZOO_INFO@log_env@679: Client environment:user.name=root 2012-06-25 15:04:58,221:11766(0x7fbdcbf5d700):ZOO_INFO@log_env@687: Client environment:user.home=/root 2012-06-25 15:04:58,221:11766(0x7fbdcbf5d700):ZOO_INFO@log_env@699: Client environment:user.dir=/root 2012-06-25 15:04:58,221:11766(0x7fbdcbf5d700):ZOO_INFO@zookeeper_init@727: Initiating client connection, host=localhost:39073 sessionTimeout=10000 watcher=0x7fbdc9f016b0 sessionId=0 sessionPasswd=<null> context=0x2c07630 flags=0 2012-06-25 15:04:58,221:11766(0x7fbdc6c5b700):ZOO_INFO@check_events@1585: initiated connection to server [127.0.0.1:39073] 2012-06-25 15:04:58,222:11766(0x7fbdc6c5b700):ZOO_ERROR@handle_socket_error_msg@1603: Socket [127.0.0.1:39073] zk retcode=-4, errno=112(Host is down): failed while receiving a server response 2012-06-25 15:05:01,558:11766(0x7fbdc6c5b700):ZOO_ERROR@handle_socket_error_msg@1579: Socket [127.0.0.1:39073] zk retcode=-4, errno=111(Connection refused): server refused to accept the client ... This seems less like a problem with juju itself but the MAAS setup before that -- cloud-init, perhaps? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in 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/maas/+bug/1015207/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
