Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transient "Service principal does not exist" error in Azure Gov #106

Closed
sstjean opened this issue Mar 25, 2021 · 0 comments · Fixed by #122
Closed

Transient "Service principal does not exist" error in Azure Gov #106

sstjean opened this issue Mar 25, 2021 · 0 comments · Fixed by #122
Assignees
Labels
AzureGov This issue is specific to the Azure Government cloud. bug Something isn't working

Comments

@sstjean
Copy link
Contributor

sstjean commented Mar 25, 2021

Description
When running mlz_tf_setup.sh in Azure Government, the service principal throws occasional errors. Either the SP wasn't created or it wasn't fully created by the time the code goes to grab the AppId. In either case, the script fails. This may be an area of code where we want to add a retry or sleep to give AAD a chance to complete.

Steps to Reproduce
Steps to reproduce the behavior:

  1. Run mlz_tf_setup.sh in MAG

Expected behavior
SP is always created

Actual behavior
SP is sometimes created, sometimes created but the code can't retrieve the AppId and sometimes creation fails.

Screenshots

Additional context
Operating System: WSL Linux 20.04
Terraform Version:
Cloud (public, Azure Government, etc.): Azure Gov

@sstjean sstjean added the bug Something isn't working label Mar 25, 2021
@Phydeauxman Phydeauxman self-assigned this Mar 26, 2021
@brooke-hamilton brooke-hamilton added the AzureGov This issue is specific to the Azure Government cloud. label Mar 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AzureGov This issue is specific to the Azure Government cloud. bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants