Adding azure credential failed with "service principal not found"

Bug #1659450 reported by Christian Muirhead
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
Medium
Unassigned

Bug Description

I ran `juju add-credential azure`, selected interactive, pasted in my subscription id and entered the verification code on the devicelogin page. After that, the CLI continued, but then failed with this error:

Authenticated as "989d74e0-34b4-49c7-bbdc-942f6ee23d5e 5c11a16f-9e9f-4ec5-83d4-ad52eb9c6d3a".
Creating/updating service principal.
ERROR finalizing credential: service principal not found

Going through the add-credential process again succeeded - maybe there needs to be a retry loop in the creating service principal step?

tags: added: azure-provider
Changed in juju:
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Anastasia (anastasia-macmood) wrote :

This looks like a duplicate of bug # 1680523. I'll mark it as such even though this report is earlier, the older report seem to have more movement.

FWIW, I believe that right now the issue is resolved.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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