cmd supercommand.go:448 failed to bootstrap model: no matching tools available

Bug #1560624 reported by Chris Gregan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
Triaged
High
Unassigned

Bug Description

Build Version/Date: 2.0-beta2-0ubuntu1~16.04.1~juju1
Environment used for testing: Xenial

Summary:
Unable to bootstrap controller due to error with stream

Steps to Reproduce:
1) juju bootstrap testcontroller-2 lxd --debug --bootstrap-series=xenial
2) juju bootstrap testcontroller-2 lxd --debug --config agent-stream=devel --bootstrap-series=xenial
3) juju bootstrap testcontroller-2 lxd --debug --config agent-stream=devel --config agent-metadata-url=https://streams.canonical.com/juju/tools --bootstrap-series=xenial

Expected result:
Xenial bootstrap successful

Actual result:
https://pastebin.canonical.com/152539/

Chris Gregan (cgregan)
tags: added: cdo-qa
Revision history for this message
Cheryl Jennings (cherylj) wrote :

I run into the same issue when using --bootstrap-series. You can use --config default-series=xenial to work around this issue for now.

Changed in juju-core:
status: New → Triaged
importance: Undecided → High
milestone: none → 2.0-beta4
tags: added: juju-release-support
Revision history for this message
Chris Gregan (cgregan) wrote :

Slightly different error with --config default-series=xenial

" ERROR cmd supercommand.go:448 failed to bootstrap model: cannot start bootstrap instance: Error adding alias ubuntu-xenial: not found"

Revision history for this message
Cheryl Jennings (cherylj) wrote :

@cgregan until beta3 is out, you'll need to manually import the image using lxd-images. (although lxd-images might not be there anymore? see: https://bugs.launchpad.net/juju-core/+bug/1558239/comments/11)

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.