Agents fail to upgrade to 2.2.7, unable to 'juju run'
Bug #1738728 reported by
Paul Gear
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Tim Penhey | ||
2.2 |
Fix Released
|
High
|
Tim Penhey | ||
2.3 |
Fix Released
|
Critical
|
Tim Penhey |
Bug Description
After an apparently-
ERROR timed out waiting for results from: machine 0, machine 1, machine 2, machine 3, machine 4, machine 5, machine 6
Changed in juju: | |
status: | New → Confirmed |
importance: | Undecided → Critical |
Changed in juju: | |
status: | Confirmed → In Progress |
milestone: | none → 2.2.8 |
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Diagnostics:
- juju-goroutines from controller machine agent: https:/ /pastebin. canonical. com/205795/
- juju-engine-report from controller machine agent: https:/ /pastebin. canonical. com/205796/
- Complete logs from controller: https:/ /private- fileshare. canonical. com/~paulgear/ lp1738728/
- juju-goroutines from hosted model machine agent: https:/ /pastebin. canonical. com/205790/
- juju-engine-report from hosted model machine agent: https:/ /pastebin. canonical. com/205791/
- Complete logs from hosted model machine agent: https:/ /pastebin. canonical. com/205794/