bundle deployments appear broken under 2.5.2 models
Bug #1821418 reported by
Drew Freiberger
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Critical
|
Heather Lanigan |
Bug Description
When running juju deploy ./bundle.yaml --dry-run, I'm receiving the error:
ERROR cannot deploy bundle: connection is shut down
Output from a juju deploy --debug and the server-side logs here:
https:/
I ruled out things like MTU/networking issues. It's happening on two discrete sites in different datacenters. One was upgraded from 2.4.1 to 2.5.2, and the other was upgraded from 2.4.4 to 2.5.2 in the past week.
Changed in juju: | |
status: | New → Incomplete |
status: | Incomplete → Triaged |
importance: | Undecided → Critical |
assignee: | nobody → Heather Lanigan (hmlanigan) |
Changed in juju: | |
status: | Triaged → In Progress |
Changed in juju: | |
status: | In Progress → Fix Committed |
To post a comment you must log in.
I think log time is not match between server and client.
There is 3 mins differences.