Canonical Juju

Upgrading juju 2.2.1 to 2.2.2 fails on Azure and vSphere

Bug #1706535 reported by Andrew Wilkins
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
Critical
Ian Booth
Canonical Juju 2.2.3

Bug Description

A recent change to version environs (https://github.com/juju/juju/commit/5fae823efd3680547b94e70f74419d2dc685d53d) introduced an upgrade step. The upgrade step should have been run for a target version of 2.2.2, but was set to 2.2. So, upgrading from 2.1.x to 2.2.2 would work, but 2.2 or 2.2.1 to to 2.2.2 would fail to run the upgrade step, which causes further issues down the line.

Andrew Wilkins (axwalk)
Changed in juju:
assignee: nobody → Andrew Wilkins (axwalk)
Revision history for this message
Ian Booth (wallyworld) wrote :

https://github.com/juju/juju/pull/7719

Changed in juju:
assignee: Andrew Wilkins (axwalk) → Ian Booth (wallyworld)
status: Triaged → In Progress
Ian Booth (wallyworld)
Changed in juju:
status: In Progress → Fix Committed
Canonical Juju QA Bot (juju-qa-bot)
Changed in juju:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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