EOF uploading charm
Bug #1543216 reported by
Aaron Bentley
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Critical
|
Cheryl Jennings | ||
juju-core |
Fix Released
|
Critical
|
Cheryl Jennings | ||
1.25 |
Fix Released
|
Critical
|
Cheryl Jennings |
Bug Description
As seen here:
http://
Juju is EOFing uploading a charm. This is an intermittent failure.
It looks timing-related. We have recently switched this test to new hardware, which may have changed timing.
Changed in juju-core: | |
assignee: | nobody → Cheryl Jennings (cherylj) |
importance: | Medium → Critical |
milestone: | none → 2.0-alpha2 |
Changed in juju-core: | |
status: | Triaged → Fix Committed |
tags: | added: tech-debt |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.0-alpha2 → none |
milestone: | none → 2.0-alpha2 |
Changed in juju-core: | |
assignee: | nobody → Cheryl Jennings (cherylj) |
importance: | Undecided → Critical |
status: | New → Fix Released |
To post a comment you must log in.
It looks like this is the same underlying cause as bug #1538583. Both the manual provider and maas provider change the mongo replicaset after bootstrap completes, causing the apiserver to drop all its connections. Here's how it happened here:
Client logs in fine: :1,"Response" :"'body redacted'"} Admin[""].Login
2016-02-08 15:12:47 DEBUG juju.apiserver apiserver.go:287 -> [11] user-admin@local 57.72784ms {"RequestId"
Client does a ModelGet just fine (part of the deploy command) :3,"Type" :"Client" ,"Version" :1,"Request" :"ModelGet" ,"Params" :"'params redacted'"} :3,"Response" :"'body redacted'"} Client[""].ModelGet
2016-02-08 15:12:47 DEBUG juju.apiserver apiserver.go:273 <- [11] user-admin@local {"RequestId"
2016-02-08 15:12:47 DEBUG juju.apiserver apiserver.go:287 -> [11] user-admin@local 3.237235ms {"RequestId"
But then we see the kiss of death for all api connections:
2016-02-08 15:12:48 INFO juju.apiserver apiserver.go:504 got error pinging mongo: EOF
After this point the apiserver will die and kill all its connections, so the next time the deploy command tries to use the API connection it has, it will get an error that it is using a closed connection ("connection is shut down").