juju 2.0 bootstrap should explain what was missing

Bug #1554797 reported by Dave Cheney
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
Medium
Unassigned

Bug Description

lucky(~/src/github.com/juju/juju) % juju bootstrap testing aws
Creating Juju controller "local.testing" on aws/us-east-1
Bootstrapping model "testing"
WARNING cannot delete default security group: cannot retrieve default security group: "juju-5fc44341-fad4-4ebd-8e7c-b2b0351296d6": The security group 'juju-5fc44341-fad4-4ebd-8e7c-b2b0351296d6' does not exist (InvalidGroup.NotFound)
ERROR failed to bootstrap model: Juju cannot bootstrap because no tools are available for your model.
You may want to use the 'agent-metadata-url' configuration setting to specify the tools location.

Juju should explain

- what model it was looking for, ie "no tools available for your mode: %s", model.String()

Then it goes on to mention something about tools location, what does this have to do with models ? How can the user resolve these two issues, are they independent, are they synonymous ?

Changed in juju-core:
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Casey Bowman (case-bowman) wrote :

I see a similar message when I try to use lxd, and it's not clear how to proceed.

```juju bootstrap lxd lxd
Creating Juju controller "local.lxd" on lxd/localhost
Bootstrapping model "lxd"
ERROR failed to bootstrap model: Juju cannot bootstrap because no tools are available for your model.
You may want to use the 'agent-metadata-url' configuration setting to specify the tools location.```

Revision history for this message
Casey Bowman (case-bowman) wrote :

For others encountering a similar problem, I was able to move forward by using the command -

juju bootstrap lxd lxd --upload-tools --config default-series=wily

(on Ubuntu 16.04 - xenial)

tags: added: 2.0-count juju-release-support
tags: added: usability
Revision history for this message
Felipe Reyes (freyes) wrote :

In my case the machine wasn't able to reach http://streams.canonical.com/juju/gui/streams/v1/index.sjson , so juju saying "connect to XXXX failed: Connection refused" would be helpful

affects: juju-core → juju
Revision history for this message
Anastasia (anastasia-macmood) wrote :

I am pretty sure we have improved failed bootstrap feedback to be a lot more helpful. Wording of bootstrap progress message has been made more explicit and descriptive too since this report was created.

I will mark it as Fixed Released. As we are currently in Juju 2.3+, should you have other cases of bootstrap messages that require further clarification, please file individual report dedicated to each case.

Changed in juju:
status: Triaged → 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.