release-juju-autopkgtests reports unknown cloud "my-controller"

Bug #1666689 reported by Curtis Hovey on 2017-02-21
4
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-release-tools
High
Unassigned

Bug Description

Recent runs of http://juju-ci.vapour.ws/job/release-juju-autopkgtests

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-series=xenial", "--config", "enable-os-upgrade=false"}
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.com/juju/juju/cmd/juju/commands/bootstrap.go:365: } {github.com/juju/juju/cmd/juju/commands/bootstrap.go:640: } {github.com/juju/juju/cmd/juju/commands/bootstrap.go:696: unknown cloud "my-controller", please try "juju update-clouds"}])
autopkgtest [16:22:17]: test current-lxd-provider: -----------------------]
autopkgtest [16:22:17]: test current-lxd-provider: - - - - - - - - - - results - - - - - - - - - -
current-lxd-provider FAIL non-zero exit status 1

The job is now disabled, but this looks like a bug in the package test that needs fixing.

Curtis Hovey (sinzui) on 2017-02-21
Changed in juju-release-tools:
status: New → Triaged
importance: Undecided → High
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers