Can't bootstrap localhost cloud

[Jacek Nykis]

I am having problems bootstrapping my juju environment:

$ juju bootstrap
Clouds
aws
aws-china
aws-gov
azure
azure-china
cloudsigma
google
joyent
localhost
rackspace

Select a cloud [localhost]: localhost

Enter a name for the Controller [jacek-localhost]:

Creating Juju controller "jacek-localhost" on localhost/localhost
Bootstrapping model "controller"
Starting new instance for initial controller
Launching instance
ERROR failed to bootstrap model: cannot start bootstrap instance: tools info mismatch ({2.0-alpha1-xenial-amd64 b67c1484745bd58e7fac6ad672a7f6e45042ebef7a1e0e995f3f0f3c2baa7d33 18556414}, {2.0-alpha2-xenial-amd64 ceb165a45206eddadc06a7c986b44a3f76195c71a317d0c87810727c71bcc0f8 18073871})
$

$ apt-cache policy juju-2.0
juju-2.0:
  Installed: 2.0~beta15-0ubuntu2.16.04.1
  Candidate: 2.0~beta15-0ubuntu2.16.04.1
  Version table:
 *** 2.0~beta15-0ubuntu2.16.04.1 500
        500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     2.0~beta4-0ubuntu2 500
        500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

[Nicholas Skaggs (nskaggs)]

Jacek, can you try with beta16? Look out for bug 1618636 however when you do so.

[Jacek Nykis (jacekn)]

beta16 is not available in xenial yet:

juju-2.0:
  Installed: 2.0~beta15-0ubuntu2.16.04.1
  Candidate: 2.0~beta15-0ubuntu2.16.04.1
  Version table:
 *** 2.0~beta15-0ubuntu2.16.04.1 500
        500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     2.0~beta4-0ubuntu2 500
        500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

[Nick Moffitt (nick-moffitt)]

Can you please advise on where to get beta16 to test with, before marking this incomplete again?

[Brendan Donegan (brendan-donegan)]

@nick-moffitt Beta17 is in the devel ppa - ppa:juju/devel. I know balloons asked for 16 but that was just the version in the PPA at the time of the comment.

[Jacek Nykis (jacekn)]

Thank you Brendan.

I can confirm that after upgrade to beta17 the problem disappeared.

[Anastasia (anastasia-macmood)]

We believe the problem was fixed in beta17 but since we cannot target to released milestones, I'll target it to current release.