TestAddLocalCharmUnauthorized mismatch

[Curtis Hovey]

As seen at
    http://reports.vapour.ws/releases/issue/56969960749a5648a5137d84

Xenial and wily (go1.6 and go 1.5), TestAddLocalCharmUnauthorized will fail like this.

client_macaroon_test.go:77:
    c.Assert(err, gc.ErrorMatches, `POST https://.*/environment/deadbeef-0bad-400d-8000-4b1d0d06f00d/charms\?series=quantal: invalid entity name or password`)
... error string = "POST https://localhost:45213/environment/deadbeef-0bad-400d-8000-4b1d0d06f00d/charms?series=quantal: Post https://localhost:45213/environment/deadbeef-0bad-400d-8000-4b1d0d06f00d/charms?series=quantal: reader has been closed"
... regex string = "POST https://.*/environment/deadbeef-0bad-400d-8000-4b1d0d06f00d/charms\\?series=quantal: invalid entity name or password"

[Dave Cheney (dave-cheney)]

I cannot reproduce this issue locally with Go 1.5 or Go 1.6 on Trusty. I will try to reproduce the issue on AWS.

If I cannot do that, I'll make a blind patch and we can see what CI thinks of it.

[Cheryl Jennings (cherylj)]

Anastasia did some work around the "invalid entity name or password" errors, and this issue hasn't been seen in CI since April.