interactive boostrap nor 'juju regions' recognise localhost as a valid cloud

Bug #1665056 reported by Chris Holcombe
32
This bug affects 7 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
High
Anastasia

Bug Description

After upgrading juju from 2.0.3 to 2.1-rc1-xenial-amd64 I'm no longer able to bootstrap a localhost environment:
juju bootstrap --debug
09:49:38 INFO juju.cmd supercommand.go:63 running juju [2.1-rc1 gc go1.6.2]
09:49:38 DEBUG juju.cmd supercommand.go:64 args: []string{"juju", "bootstrap", "--debug"}
Clouds
aws
aws-china
aws-gov
azure
azure-china
cloudsigma
google
joyent
localhost
rackspace
serverstack

Select a cloud [localhost]: localhost

09:49:41 ERROR cmd supercommand.go:458 cloud localhost not found
09:49:41 DEBUG cmd supercommand.go:459 (error details: [{github.com/juju/juju/cmd/juju/commands/bootstrap.go:358: } {github.com/juju/juju/cmd/juju/commands/bootstrap.go:1008: } {github.com/juju/juju/cloud/clouds.go:213: cloud localhost not found}])

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

@Chris Holcombe,
In order for us to reproduce, could you please clarify how you upgraded from 2.0.3 to 2.1-rc1?

Changed in juju:
status: New → Incomplete
Revision history for this message
Chris Holcombe (xfactor973) wrote : Re: [Bug 1665056] Re: cloud localhost not found

I didn't do anything special. Just installed the ppa for 2.1-rc1 and
installed it via apt install juju. After that I tried to bootstrap
localhost and it failed.

On 02/20/2017 01:24 AM, Anastasia wrote:
> @Chris Holcombe,
> In order for us to reproduce, could you please clarify how you upgraded from 2.0.3 to 2.1-rc1?
>
> ** Changed in: juju
> Status: New => Incomplete
>

Revision history for this message
Anastasia (anastasia-macmood) wrote : Re: cloud localhost not found

@Chris,

Could you please provide an output from 'juju clouds'?

Revision history for this message
Chris Holcombe (xfactor973) wrote : Re: [Bug 1665056] Re: cloud localhost not found

I'm not sure how useful the output is now that I'm back on 2.0.3. I
downgraded and purged all the config files so I could get back working.
Here's what it looks like now:

juju clouds
Cloud Regions Default Type Description
aws 11 us-east-1 ec2 Amazon Web Services
aws-china 1 cn-north-1 ec2 Amazon China
aws-gov 1 us-gov-west-1 ec2 Amazon (USA Government)
azure 18 centralus azure Microsoft Azure
azure-china 2 chinaeast azure Microsoft Azure China
cloudsigma 5 hnl cloudsigma CloudSigma Cloud
google 6 us-east1 gce Google Cloud Platform
joyent 6 eu-ams-1 joyent Joyent Cloud
rackspace 6 dfw rackspace Rackspace Cloud
localhost 1 localhost lxd LXD Container Hypervisor

Try 'list-regions <cloud>' to see available regions.
'show-cloud <cloud>' or 'regions --format yaml <cloud>' can be used to
see region endpoints.
'add-cloud' can add private clouds or private infrastructure.
Update the known public clouds with 'update-clouds'.

On 02/22/2017 03:16 AM, Anastasia wrote:
> @Chris,
>
> Could you please provide an output from 'juju clouds'?
>

Revision history for this message
Anastasia (anastasia-macmood) wrote : Re: cloud localhost not found

@Chris,

Yes, the command output would have been useful on a broken system when you were getting "cloud localhost not found".

At this stage, I cannot reproduce this.

Revision history for this message
Chris Holcombe (xfactor973) wrote :

I just hit it again on my laptop.

chris@chris-ThinkPad-T410s:~$ juju bootstrap
Clouds
aws
aws-china
aws-gov
azure
azure-china
cloudsigma
google
joyent
localhost
rackspace

Select a cloud [localhost]: localhost

ERROR cloud localhost not found
chris@chris-ThinkPad-T410s:~$ juju --version
2.1-rc1-xenial-amd64
chris@chris-ThinkPad-T410s:~$ juju clouds
Cloud Regions Default Type Description
aws 14 us-east-1 ec2 Amazon Web Services
aws-china 1 cn-north-1 ec2 Amazon China
aws-gov 1 us-gov-west-1 ec2 Amazon (USA Government)
azure 18 centralus azure Microsoft Azure
azure-china 2 chinaeast azure Microsoft Azure China
cloudsigma 5 hnl cloudsigma CloudSigma Cloud
google 4 us-east1 gce Google Cloud Platform
joyent 6 eu-ams-1 joyent Joyent Cloud
rackspace 6 dfw rackspace Rackspace Cloud
localhost 1 localhost lxd LXD Container Hypervisor

Try 'list-regions <cloud>' to see available regions.
'show-cloud <cloud>' or 'regions --format yaml <cloud>' can be used to see region endpoints.
'add-cloud' can add private clouds or private infrastructure.
Update the known public clouds with 'update-clouds'.

Revision history for this message
Chris Holcombe (xfactor973) wrote :

Here's the debug output:
chris@chris-ThinkPad-T410s:~$ juju bootstrap --debug
21:31:24 INFO juju.cmd supercommand.go:63 running juju [2.1-rc1 gc go1.6.2]
21:31:24 DEBUG juju.cmd supercommand.go:64 args: []string{"juju", "bootstrap", "--debug"}
Clouds
aws
aws-china
aws-gov
azure
azure-china
cloudsigma
google
joyent
localhost
rackspace

Select a cloud [localhost]: localhost

21:31:27 ERROR cmd supercommand.go:458 cloud localhost not found
21:31:27 DEBUG cmd supercommand.go:459 (error details: [{github.com/juju/juju/cmd/juju/commands/bootstrap.go:358: } {github.com/juju/juju/cmd/juju/commands/bootstrap.go:1008: } {github.com/juju/juju/cloud/clouds.go:213: cloud localhost not found}])

summary: - cloud localhost not found
+ interactive boostrap does not recognise localhost as a valid cloud
Changed in juju:
status: Incomplete → Triaged
importance: Undecided → High
milestone: none → 2.2.0
Revision history for this message
Anastasia (anastasia-macmood) wrote :

Re-titled the bug as the same occurs for 'juju regions localhost'. Both have the same cause and will require the same fix.

summary: - interactive boostrap does not recognise localhost as a valid cloud
+ interactive boostrap nor 'juju regions' recognise localhost as a valid
+ cloud
Changed in juju:
status: Triaged → In Progress
assignee: nobody → Anastasia (anastasia-macmood)
milestone: 2.2.0 → 2.2-rc1
Revision history for this message
Anastasia (anastasia-macmood) wrote :

PR against develop (2.2-rc1): https://github.com/juju/juju/pull/7039

Changed in juju:
status: In Progress → Fix Committed
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.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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