Upgrade is broken in 1.22: connection shutdown

Bug #1474931 reported by Curtis Hovey
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
Invalid
Low
Unassigned
1.22
Fix Released
Critical
Ian Booth

Bug Description

No call to juju-upgrade has passed in 1.22 as ov commit 4c4ccd9
    http://reports.vapour.ws/releases/2882

(Ignore the gce and vivid upgrade tests, they were skipped because 1.22 doesn't support them.)

Here are a few examples of the failures
    http://reports.vapour.ws/releases/2882/job/local-upgrade-trusty-amd64/attempt/1356
    http://reports.vapour.ws/releases/2882/job/local-upgrade-precise-amd64/attempt/2787
    http://reports.vapour.ws/releases/2882/job/aws-upgrade-trusty-amd64/attempt/2233

Curtis Hovey (sinzui)
Changed in juju-core:
importance: Critical → Undecided
importance: Undecided → Low
status: Triaged → Invalid
Revision history for this message
Canonical Juju QA Bot (juju-qa-bot) wrote : Fix Released in juju-core 1.22

Juju-CI verified that this issue is Fix Released in juju-core 1.22:
    http://reports.vapour.ws/releases/2888

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.