bootstrap fails to honor config for agent-version

Bug #1696835 reported by Richard Harding
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
High
Anastasia

Bug Description

From the juju bootstrap --help

Examples
    ...
    juju bootstrap --config agent-version=1.25.3 aws joe-us-east-1

When I attempt to do this with an RC2 client:

    juju bootstrap --config agent-version=2.1.3 aws upgrade
    Creating Juju controller "upgrade" on aws/us-east-1
    Looking for packaged Juju agent version 2.2-rc1 for amd64

It does not function. I've verfied after bootstrap:

    juju controllers
    upgrade* default admin superuser aws/us-east-1 2 1 none 2.2-rc1

I'd like to bootstrap a 2.1.3 so that I can test and write directions around upgrading using juju migrate. I'm not able to do that from the single client as I'd expected to be able to.

Revision history for this message
Richard Harding (rharding) wrote :

In checking this out there's the --agent-version flag on bootstrap itself:

    juju bootstrap --agent-version=2.1.3 aws upgradeneeded
    ERROR requested agent version major.minor mismatch

I'm guessing this is saying that my 2.2-rc1 is not able to request agents from 2.1.3?

Revision history for this message
John A Meinel (jameinel) wrote :

We need to update the help text, because I'm pretty sure it is "juju bootstrap --agent-version X" rather than "--config" at this point.

As for RC vs Stable, we still have the bug where if you're using a 'devel' version (anything with an 'rc/beta/etc' then it only sees beta agents as targets for deploy).

Also for *bootstrap* people have generally pushed pretty hard that we have to bootstrap the exact version as the client, and then possibly 'upgrade' to the requested version. And since you're using a newer client, we probably wouldn't let you downgrade the controller anyway.
(For example, 2.2 breaks bootstrap wrt 2.1 because it added a new mandatory field, so a 2.1 client couldn't bootstrap a 2.2 agent anyway, you have to go through the upgrade step.)

I think the docs we could fix, actually selecting the agent version is a bit trickier to support in all cases.

Generally within .patch versions, we could probably do it, but major.minor is probably not ever really supported.

Changed in juju:
importance: Undecided → High
status: New → Triaged
Revision history for this message
Anastasia (anastasia-macmood) wrote :

The problem is the a client can only bootstrap using its own major.minor versions. So, a 2.1 client can only bootstrap 2.1.x agents; 2.2 can only bootstrap 2.2.x agents, etc.

I have updated the error message at bootstrap: https://github.com/juju/juju/pull/7911

Changed in juju:
status: Triaged → Fix Committed
assignee: nobody → Anastasia (anastasia-macmood)
milestone: none → 2.3-beta1
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.

Other bug subscribers

Remote bug watches

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