TestAddLocalCharmUnauthorized mismatch

Bug #1550819 reported by Curtis Hovey
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
High
Dave Cheney

Bug Description

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"

Curtis Hovey (sinzui)
Changed in juju-core:
milestone: 2.0-beta2 → 2.0-beta3
Curtis Hovey (sinzui)
Changed in juju-core:
milestone: 2.0-beta3 → 2.0-beta4
tags: added: 2.0-count
Revision history for this message
Dave Cheney (dave-cheney) wrote :

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.

Changed in juju-core:
assignee: nobody → Dave Cheney (dave-cheney)
status: Triaged → In Progress
Changed in juju-core:
milestone: 2.0-beta4 → 2.0-rc1
Curtis Hovey (sinzui)
Changed in juju-core:
milestone: 2.0-beta5 → 2.0-rc1
Curtis Hovey (sinzui)
Changed in juju-core:
milestone: 2.0-beta6 → 2.0-beta7
Curtis Hovey (sinzui)
Changed in juju-core:
milestone: 2.0-beta7 → 2.0-beta8
Curtis Hovey (sinzui)
Changed in juju-core:
milestone: 2.0-beta8 → 2.0-beta9
Curtis Hovey (sinzui)
Changed in juju-core:
milestone: 2.0-beta9 → 2.0-beta10
Curtis Hovey (sinzui)
Changed in juju-core:
milestone: 2.0-beta10 → 2.0-beta11
Curtis Hovey (sinzui)
Changed in juju-core:
milestone: 2.0-beta11 → 2.0-beta12
Revision history for this message
Cheryl Jennings (cherylj) wrote :

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

Changed in juju-core:
status: In Progress → Fix Released
affects: juju-core → juju
Changed in juju:
milestone: 2.0-beta12 → none
milestone: none → 2.0-beta12
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.