Critical bugs blocking 1.17.0

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2013-12-18 1:50, Curtis Hovey-Canonical wrote:
> Good news (of sorts).
> 
> On Tue, Dec 17, 2013 at 2:08 PM, Curtis Hovey-Canonical 
> <curtis at canonical.com> wrote: ...
>> upgrade is broken on hp and canonistack 
>> https://bugs.launchpad.net/bugs/1260452 This bug reports that
>> tools cannot be found, or that 
>> https://streams.canonical.com/juju/tools/streams/v1/index.json
>> 404s. Since every env specifies the tools-url to be the testing
>> location, and it has the tools, I cannot think of why Juju is not
>> honouring the instruction.

I don't know that bit yet, but I am surprised to see the failure be:
https://streams.canonical.com/juju/tools/streams/v1/index.json
                              ^^^^
Note the juju/ in the URL. If you actually go to streams.canonical.com
the files are at:
https://streams.canonical.com/tools/streams/v1/index.json

Though it may be that we intend them to be at the new place.

As for what is happening, we *do* log enough information in '--debug'
mode, but Aaron mentioned he's not comfortable using it because it
logs the full ENV which means secrets end up in the log file.

Is there any way to trigger a run and either privately collect the
log, or sanitize it somehow? It would tell us exactly what URLs it is
trying, and might give a clear indication of what is failing. (Is it
failing because of a typo during the lookup, is it just skipping some
step, etc.)

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlKxTbgACgkQJdeBCYSNAAPSPgCdE+lAy7/u9nZJw3src3UlOztO
xfAAnRCl+dCMAfRk2XOA9D0ElPQ9uMwc
=pofB
-----END PGP SIGNATURE-----