upgrade-model should default to using controller version

Bug #1879573 reported by Paul Collins
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
Low
Unassigned

Bug Description

I have a controller I bootstrapped with 2.8-rc1. I was able to upgrade the controller to 2.8-rc2 with juju upgrade-controller --agent-stream proposed.

However, Juju doesn't seem to be able to automatically upgrade the model hosted in that controller:

[agnew(~)] juju upgrade-model
best version:
    2.8.1.3647
ERROR model cannot be upgraded to 2.8.1.3647 while the controller is 2.8-rc2: upgrade 'controller' model first
[agnew(~)] juju upgrade-model --agent-stream proposed
best version:
    2.9-beta1.3650
ERROR model cannot be upgraded to 2.9-beta1.3650 while the controller is 2.8-rc2: upgrade 'controller' model first
[agnew(~)] _

However:

[agnew(~)] juju upgrade-model --agent-version 2.8-rc2
best version:
    2.8-rc2
started upgrade to 2.8-rc2
[agnew(~)] _

This seems like something Juju should be able to work out for itself.

Revision history for this message
Paul Collins (pjdc) wrote :

I just bootstrapped a fresh rc1 controller with the rc2 client to test something else, and now I can't upgrade at all:

[agnew(~)] juju upgrade-controller --agent-stream proposed
best version:
    2.8-rc2
started upgrade to 2.8-rc2
[agnew(~)] juju status -m controller
Model Controller Cloud/Region Version SLA Timestamp
controller betabeta localhost/localhost 2.8-rc2 unsupported 10:29:38+12:00

Machine State DNS Inst id Series AZ Message
0 started 10.9.8.197 juju-ffacfd-0 bionic Running

[agnew(~)] juju upgrade-model --agent-version 2.8-rc2
ERROR no matching agent versions available
[agnew(~)] _

I wondered if the local streams needed a prod, but:

[agnew(~)] juju upgrade-model --agent-stream proposed
best version:
    2.9-beta1.3650
ERROR model cannot be upgraded to 2.9-beta1.3650 while the controller is 2.8-rc2: upgrade 'controller' model first
[agnew(~)] juju upgrade-model --agent-version 2.8-rc2
ERROR no matching agent versions available
[agnew(~)] _

However, this worked:

[agnew(~)] juju upgrade-model --agent-version 2.8-rc2 --agent-stream proposed
best version:
    2.8-rc2
started upgrade to 2.8-rc2
[agnew(~)] _

Weird that it worked without it on my previous controller.

Revision history for this message
Ian Booth (wallyworld) wrote :

Juju uses --agent-stream similar to how snap uses --channel.
When you run upgrade-controller, Juju will filter the agents it selects from based on the user's desired level of risk; that's why juju doesn't work it out for itself; it must be a user driven decision.

It does look like there's an issue though in that --agent-stream proposed should not have presented "2.9-beta1.3650" as a choice.

Changed in juju:
milestone: none → 2.8.1
importance: Undecided → High
status: New → Triaged
Revision history for this message
Tim Penhey (thumper) wrote :

When you just run 'juju upgrade-model' with no args, the model should just be upgraded to the controller version with no simplestreams checks.

Ian Booth (wallyworld)
Changed in juju:
milestone: 2.8.1 → 2.8.2
Ian Booth (wallyworld)
summary: - k8s model upgrade rc1 to rc2 on rc2 LXD controller requires --agent-
- version
+ upgrade-model should default to using controller version
tags: added: upgrade-juju
Changed in juju:
milestone: 2.8.2 → 2.8.3
Pen Gale (pengale)
Changed in juju:
milestone: 2.8.4 → none
Revision history for this message
Canonical Juju QA Bot (juju-qa-bot) wrote :

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.

Changed in juju:
importance: High → Low
tags: added: expirebugs-bot
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.