release-juju-autopkgtests reports unknown cloud "my-controller"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-release-tools |
Triaged
|
High
|
Unassigned |
Bug Description
Recent runs of http://
Testing juju bootstrap:
Since Juju 2 is being run for the first time, downloading latest cloud information.
Fetching latest public cloud list...
Updated your list of public clouds with 2 cloud regions deleted:
deleted cloud region:
- aws/ca-central-1
- aws/eu-west-2
16:22:16 INFO juju.cmd supercommand.go:63 running juju [2.2-alpha1 gc go1.6.2]
16:22:16 DEBUG juju.cmd supercommand.go:64 args: []string{"juju", "bootstrap", "my-controller", "lxd", "--debug", "--config", "default-
16:22:16 INFO cmd cmd.go:141 cloud "my-controller" not found, trying as a provider name
16:22:16 ERROR cmd supercommand.go:458 unknown cloud "my-controller", please try "juju update-clouds"
16:22:16 DEBUG cmd supercommand.go:459 (error details: [{github.
autopkgtest [16:22:17]: test current-
autopkgtest [16:22:17]: test current-
current-
The job is now disabled, but this looks like a bug in the package test that needs fixing.
Changed in juju-release-tools: | |
status: | New → Triaged |
importance: | Undecided → High |