can't upgrade k8s model after upgrading controller
Bug #1867224 reported by
Ian Booth
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Ian Booth |
Bug Description
As reported in bug 1865416
I can't upgrade existing models once the controller has been upgraded to a beta:
$ juju upgrade-juju
best version:
2.8-beta1.3284
ERROR model cannot be upgraded to 2.8-beta1.3284 while the controller is 2.8-beta1: upgrade 'controller' model first
$
But if there's anything deployed in the model, LP:1865439 means that I can't destroy it either, without nuking the whole controller (or at least, I haven't yet found a way to do so).
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
This issue here was that a lack of filtering when looking at available docker images for the juju operator meant that images for CI testing were being considered, and these had tags including a build number which messed up the upgrade version checks. By adding simple streams filtering in bug 1865416, I think this issue is addressed. A simple test worked.