upgrade-juju --dry-run ignores agent-stream

[Nicholas Skaggs]

Bootstrap a controller with proposed stream, and dry-run will lie to you about what it's going to upgrade to.

/usr/lib/juju-2.2.6/bin/juju bootstrap aws aws --config agent-stream=proposed
/usr/lib/juju-2.2.6/bin/juju upgrade-juju --dry-run
upgrade to this version by running
    juju upgrade-juju --agent-version="2.3.0"
/usr/lib/juju-2.2.6/bin/juju status -m controller
Model Controller Cloud/Region Version SLA
controller aws aws/us-east-1 2.2.6 unsupported

App Version Status Scale Charm Store Rev OS Notes

Unit Workload Agent Machine Public address Ports Message

Machine State DNS Inst id Series AZ Message
0 started 35.153.203.43 i-0b83394cd973df00d xenial us-east-1a running

/usr/lib/juju-2.2.6/bin/juju upgrade-juju -m controller
CRITICAL ********** SetModelAgentVersion: 2.3.1 false
started upgrade to 2.3.1

EDIT: Interestingly, bootstrapping a 2.3.0 controller, with proposed streams (which as of right now has 2.3.1, but released doesn't), you get this:

/usr/lib/juju-2.3.0/bin/juju upgrade-juju --dry-run

upgrade to this version by running
    juju upgrade-juju

Are we missing the version print also?

[Ian Booth (wallyworld)]

This is fixed in 2.3 but won't be fixed in 2.2.6 unless we choose to backport and do another 2.2.x release.
In 2.3, there's no need to specify the agent version so we no longer print it.