1.9.14 flakiness

[William Reade]

This issue is for collecting 1.9.14 strangeness information in the hope that patterns will become apparent.

[William Reade (fwereade)]

fwereade has successfully bootstrapped and deployed in us-east-1, but seen occasional failures with:

2013/04/18 14:00:46 ERROR command failed: cannot find tools: use of closed network connection

fwereade has successfully bootstrapped and deployed in eu-west-1 without errors.

fwereade has a bootstrap node that appears to be working perfectly in ap-southeast-1, but cannot connect to it due to a 100% failure rate looking up the bootstrap instance (which really does exist):

william@diz:~$ /usr/bin/juju status --debug
2013/04/18 14:06:23 INFO environs/ec2: opening environment "apse2"
2013/04/18 14:06:26 INFO environs/ec2: waiting for DNS name(s) of state server instances [i-c75698fa]
2013/04/18 14:06:31 ERROR command failed: no instances found
error: no instances found

[Frank Mueller (themue)]

TheMue so far successfully bootstrapped and installed on us-east-1 and us-west-2 with precise.

[Dimiter Naydenov (dimitern)]

I can confirm 1.19.14-amd63-quantal1 from the ppa:juju/devel is broken for me on quantal/64. With various changes to env.yaml and arguments I get mostly "use of closed network connection" error from bootstrap and sync-tools. No --upload-tools, --dev or --series, just "/usr/bin/juju bootstrap --debug -v -e amazon".

Here is the paste: http://paste.ubuntu.com/5718578/ (tried on us-east-1 and eu-west-1)
The same error is reported if I try /usb/bin/juju sync-tools -v --debug.

I tried all regions at first: us-east-1, us-west-1,2, eu-west-1, ap-southeast-1,2, ap-northeast-1, sa-east-1; with custom "public-bucket". All give the same error: "no compatible tools found" - http://paste.ubuntu.com/5718528/

[Frank Mueller (themue)]

us-west-1 and eu-west-1 also bootstrap and deploy fine.

[Dave Cheney (dave-cheney)]

Thank you all for your feedback.

I am strongly of the opinion that the region is not a factor in this; because we haven't even started to talk to the ec2 service at this point, only the s3 public bucket which as a known location.

At this point 1.9.14 has been the top in the repo for several days, so people installing from PPA will have been getting this version so there is little point in _not_ releasing the release notes at this time.

The next steps for me are to add debugging to the tools searching to find out what is going on.

[William Reade (fwereade)]

1.9.14 is a pre-release development version and is not supported now.