Comment 0 for bug 1365035

Revision history for this message
David Britton (dpb) wrote :

I've got this error a few times now with 1.20.6, and I don't think it's representative of an actual failure with the network. This is all on a private network that has been working fine before 1.20.6. Short paste here, longer paste attached:

Logging to /var/log/cloud-init-output.log on remote host
Running apt-get update
Running apt-get upgrade
Installing package: git
Installing package: curl
Installing package: cpu-checker
Installing package: bridge-utils
Installing package: rsyslog-gnutls
Fetching tools: curl -sSfw 'tools from %{url_effective} downloaded: HTTP %{http_code}; time %{time_total}s; size %{size_download} bytes; speed %{speed_download} bytes/s ' --retry 10 -o $bin/tools.tar.gz 'https://streams.canonical.com/juju/tools/releases/juju-1.20.6-trusty-amd64.tgz'
Bootstrapping Juju machine agent
Timeout, server tesla.beretstack not responding.
2014-09-02 20:51:07 ERROR juju.provider.common bootstrap.go:119 bootstrap failed: subprocess encountered error code 255
Stopping instance...
2014-09-02 20:51:07 INFO juju.cmd cmd.go:113 Bootstrap failed, destroying environment
2014-09-02 20:51:07 INFO juju.provider.common destroy.go:15 destroying environment "beretstack-0"
2014-09-02 20:51:07 ERROR juju.cmd supercommand.go:323 subprocess encountered error code 255
2014-09-02 15:51:07 Saving off $JUJU_HOME -> /tmp/jenkins/workspace/bootstrap-dense/build/jenkins/beretstack-0
ERROR Unable to connect to environment "beretstack-0".

If I had the option to leave the machine up (coming in 1.20.7+?) it would be helpful, since I can't repeat this every time.