On Tue, May 13, 2014 at 4:04 PM, Andrew Wilkins < andrew.wilk...@canonical.com> wrote:
> On Tue, May 13, 2014 at 12:41 PM, John Meinel <j...@arbash-meinel.com>wrote: > >> You might be running into this: >> >> http://askubuntu.com/questions/458535/how-to-change-juju-bootstrap-time-from-the-10min-it-gives-you >> John >> =:-> >> >> >> On Mon, May 12, 2014 at 4:47 PM, boyd yang <boyd.y...@gmail.com> wrote: >> >>> Hello, >>> >>> I got juju bootstrap error. >>> I used Ubuntu 14.04 LTS. >>> How to fix this? >>> Thanks! >>> >>> root@maas:/home/ceph# juju bootstrap --show-log >>> 2014-05-12 12:21:06 INFO juju.cmd supercommand.go:297 running >>> juju-1.18.1-trusty-amd64 [gc] >>> 2014-05-12 12:21:06 INFO juju.environs open.go:177 environment info >>> already exists; using New not Prepare >>> 2014-05-12 12:21:06 INFO juju.environs.bootstrap bootstrap.go:46 >>> bootstrapping environment "maas" >>> 2014-05-12 12:21:06 INFO juju.environs.tools tools.go:186 filtering >>> tools by released version >>> 2014-05-12 12:21:06 INFO juju.environs.tools tools.go:86 reading tools >>> with major.minor version 1.18 >>> 2014-05-12 12:21:06 INFO juju.environs.tools tools.go:97 filtering tools >>> by series: trusty >>> 2014-05-12 12:21:06 INFO juju.utils http.go:55 hostname SSL verification >>> enabled >>> 2014-05-12 12:21:26 INFO juju.utils http.go:55 hostname SSL verification >>> enabled >>> 2014-05-12 12:21:30 INFO juju.utils http.go:55 hostname SSL verification >>> enabled >>> 2014-05-12 12:21:33 INFO juju.utils http.go:55 hostname SSL verification >>> enabled >>> 2014-05-12 12:22:18 INFO juju.environs.bootstrap bootstrap.go:58 picked >>> newest version: 1.18.3 >>> Launching instance >>> 2014-05-12 12:22:20 WARNING juju.provider.maas environ.go:233 picked >>> arbitrary tools &{"1.18.3-trusty-amd64" " >>> https://streams.canonical.com/juju/tools/releases/juju-1.18.3-trusty-amd64.tgz"; >>> "b54decd84ad21c5a3b924448bc865fa53f6552d230a89ed01d929db4fa8659b6" >>> %!q(int64=7385591)} >>> - /MAAS/api/1.0/nodes/node-a2791000-d375-11e3-9bfb-c81f66b95a0e/ >>> Waiting for address >>> Attempting to connect to jdreb.maas:22 >>> Attempting to connect to 192.168.10.12:22 >>> 2014-05-12 12:32:20 ERROR juju.provider.common bootstrap.go:123 >>> bootstrap failed: waited for 10m0s without being able to connect: >>> /var/lib/juju/nonce.txt does not exist >>> Stopping instance... >>> Bootstrap failed, destroying environment >>> 2014-05-12 12:32:21 INFO juju.provider.common destroy.go:14 destroying >>> environment "maas" >>> 2014-05-12 12:32:21 ERROR juju.cmd supercommand.go:300 waited for 10m0s >>> without being able to connect: /var/lib/juju/nonce.txt does not exist >>> >> > The end of the last line there indicates something has gone wrong while > initialising the first MAAS node. We run a cloud-init script that creates > the nonce.txt file, which we use to verify the machine's identity. > > It looks like a bug in either Juju or MAAS. Do you know how you got into > this situation? > > Cheers, > Andrew > I should also note that there is a possibility that extending the timeout, as suggested by John, may resolve the issue. It could be that cloud-init is still running, and the nonce.txt file just hasn't been written *yet*.
-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
