juju azure auth stopped working
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Anastasia |
Bug Description
I have an environment where I wanted to add new unit but I'm getting 401 errors:
$ juju add-unit --debug myservice
11:19:12 INFO juju.cmd supercommand.go:63 running juju [2.2.6 gc go1.8]
11:19:12 DEBUG juju.cmd supercommand.go:64 args: []string{"juju", "add-unit", "--debug", "myservice"}
11:19:12 INFO juju.juju api.go:67 connecting to API addresses: [1.2.3.4:17070 192.168.16.4:17070]
11:19:13 DEBUG juju.api apiclient.go:863 successfully dialed "wss://
11:19:13 INFO juju.api apiclient.go:617 connection established to "wss://
11:19:14 DEBUG juju.api monitor.go:35 RPC connection died
ERROR cannot add unit 1/1 to application "myservice": cannot add unit to application "myservice": getting instance types: listing VM sizes: autorest#
11:19:14 DEBUG cmd supercommand.go:459 error stack:
cannot add unit 1/1 to application "myservice": cannot add unit to application "myservice": getting instance types: listing VM sizes: autorest#
github.
github.
I rerun "juju add-credential azure" in controller and workload models but that did not help.
I also wanted to upgrade juju since I'm not on the latest version but that's also blocked by the same problem:
$ juju upgrade-juju
no prepackaged tools available, using local agent binary 2.2.6.1
CRITICAL ********** SetModelAgentVe
ERROR cannot make API call to provider: autorest#
My juju CLI version is 2.2.6-trusty-amd64 and the controller model is on 2.2.3
tags: | added: canonical-is |
Changed in juju: | |
status: | In Progress → Incomplete |
assignee: | Anastasia (anastasia-macmood) → nobody |
Changed in juju: | |
status: | Confirmed → In Progress |
assignee: | nobody → Anastasia (anastasia-macmood) |
Changed in juju: | |
status: | Fix Committed → Fix Released |
Juju is returning the cloud provider error. Given this worked in the past, I would suspect an issue with azure or your credentials.