Misleading error when agent-version doesn't match juju version on bootstrap

Bug #1492396 reported by Aaron Bentley
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
Won't Fix
Low
Unassigned

Bug Description

When the agent-version specified in environments.yaml does not match the juju client version, it simply says "Juju cannot bootstrap because no tools are available for your environment.
You may want to use the 'agent-metadata-url' configuration setting to specify the tools location."

This is wrong. There are tools available for the environment, but Juju doesn't want to use them. Setting agent-metadata-url cannot possibly change this.

Instead, it should say something like 'Juju cannot bootstrap because environment agent-version "1.23.2" is not in the 1.24 series'.

$ juju --version
1.24.5-vivid-amd64

$ juju bootstrap -e awsx --show-log
2015-09-04 16:41:53 INFO juju.cmd supercommand.go:37 running juju [1.24.5-vivid-amd64 gc]
2015-09-04 16:41:53 INFO juju.provider.ec2 provider.go:49 opening environment "awsx"
2015-09-04 16:41:54 INFO juju.network network.go:194 setting prefer-ipv6 to false
Bootstrapping environment "awsx"
2015-09-04 16:41:57 INFO juju.environs.tools tools.go:86 reading tools with major.minor version 1.24
2015-09-04 16:41:57 INFO juju.environs.tools tools.go:94 filtering tools by version: 1.23.2
Bootstrap failed, destroying environment
2015-09-04 16:41:57 INFO juju.provider.common destroy.go:15 destroying environment "awsx"
2015-09-04 16:41:58 ERROR juju.cmd supercommand.go:430 failed to bootstrap environment: Juju cannot bootstrap because no tools are available for your environment.
You may want to use the 'agent-metadata-url' configuration setting to specify the tools location.

$ $HOME/canonical/juju-versions/1.23.2/usr/lib/juju-1.23.2/bin/juju --version
1.23.2-vivid-amd64
$ $HOME/canonical/juju-versions/1.23.2/usr/lib/juju-1.23.2/bin/juju bootstrap -e awsx --show-log
2015-09-04 16:52:11 INFO juju.cmd supercommand.go:37 running juju [1.23.2-vivid-amd64 gc]
2015-09-04 16:52:12 INFO juju.provider.ec2 provider.go:49 opening environment "awsx"
2015-09-04 16:52:12 INFO juju.network network.go:194 setting prefer-ipv6 to false
Bootstrapping environment "awsx"
2015-09-04 16:52:15 INFO juju.environs.tools tools.go:86 reading tools with major.minor version 1.23
2015-09-04 16:52:15 INFO juju.environs.tools tools.go:94 filtering tools by version: 1.23.2
Starting new instance for initial state server
Launching instance
...

tags: added: simplestreams
Changed in juju-core:
status: Triaged → Won't Fix
Revision history for this message
Aaron Bentley (abentley) wrote :

Why is this won't fix?

Revision history for this message
Anastasia (anastasia-macmood) wrote :

@Aaron Bentley,
"juju-core" is an old Juju 1 project. We only accept Critical bugs here that may still need to be addressed in 1.25 series.

"juju" is the new project for bugs/issues/suggestions for Juju 2. An email went out couple of months ago saying that we will be moving some bugs over, the rest will be closed "eventually" unless people are interested in having us addressing their concerns in Juju 2. "Eventually" is now :D since Juju 2 was released last week \o/

I am happy to re-target this to "juju" if you would like us to keep it.

Revision history for this message
Aaron Bentley (abentley) wrote : Re: [Bug 1492396] Re: Misleading error when agent-version doesn't match juju version on bootstrap

I think we should re-target it to juju.

What are the criteria for which bugs get moved over to juju 2?

Aaron

On 2016-10-17 09:32 AM, Anastasia wrote:
> @Aaron Bentley,
> "juju-core" is an old Juju 1 project. We only accept Critical bugs here that may still need to be addressed in 1.25 series.
>
> "juju" is the new project for bugs/issues/suggestions for Juju 2. AnIt
> email went out couple of months ago saying that we will be moving some
> bugs over, the rest will be closed "eventually" unless people are
> interested in having us addressing their concerns in Juju 2.
> "Eventually" is now :D since Juju 2 was released last week \o/
>
> I am happy to re-target this to "juju" if you would like us to keep it.
>

Revision history for this message
Anastasia (anastasia-macmood) wrote :

Criteria was widely circulated via mailing list to juju-dev and has been used by QA team when moving bugs.

Since there have been a lot movement in this area, Juju 2 would have different approach/message/behavior for this use case.

Please re-test with Juju 2. If you are still concerned, please file a new bug against "juju".

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.