juju bootstrap fails - Waiting for API to become available ERROR cannot get all blocks: EOF

[Larry Michel]

We have been seeing a number of failures with juju 1.24.0 when doing juju bootstrap for deploying OpenStack.

2015-06-21 07:53:02,484 [INFO] oil_ci.juju.client: Boostrapping new environment
Bootstrapping environment "ci-oil-slave11"
Starting new instance for initial state server
Launching instance
WARNING no architecture was specified, acquiring an arbitrary node
WARNING no architecture was specified, acquiring an arbitrary node
WARNING no architecture was specified, acquiring an arbitrary node
WARNING no architecture was specified, acquiring an arbitrary node
 - /MAAS/api/1.0/nodes/node-9e9e2eb8-c4cd-11e3-8102-00163efc5068/
Installing Juju agent on bootstrap instance
Waiting for address
Attempting to connect to hayward-28.oil:22
Attempting to connect to hayward-28.oil:22
Attempting to connect to 10.245.0.172:22
Warning: Permanently added 'hayward-28.oil' (ECDSA) to the list of known hosts.
Logging to /var/log/cloud-init-output.log on remote host
Running apt-get update
Running apt-get upgrade
Installing package: curl
Installing package: cpu-checker
Installing package: bridge-utils
Installing package: rsyslog-gnutls
Installing package: cloud-utils
Installing package: cloud-image-utils
Installing package: tmux
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.24.0-trusty-amd64.tgz]>
Bootstrapping Juju machine agent
Starting Juju machine agent (jujud-machine-0)
Bootstrap agent installed
Waiting for API to become available
ERROR cannot get all blocks: EOF
2015-06-21 08:07:03,811 [ERROR] oil_ci.juju.client: Calling "juju bootstrap" failed!
2015-06-21 08:07:03,811 [ERROR] oil_ci.cli: Deployment failed:

[Curtis Hovey (sinzui)]

This may relate to bug 1455260 where clients cannot assume connections are permanent and need to be retried. Unlike the other issue, implicit upgrading is not involved.

[Andreas Hasenack (ahasenack)]

I saw something similar. Exit status is 1 after it was waiting or retrying for a while, and eventually failed. But bootstrap was working in the end: https://pastebin.canonical.com/134139/

[Larry Michel (lmic)]

To answer Ian's question in the duplicate bug about frequency, we have hit the EOF failure in 30 out of last 363 builds.