Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
"az keyvault secret set" failed with error "Max retries exceeded attempting to connect to vault"
See original GitHub issueThis is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az keyvault secret set
Errors:
Max retries exceeded attempting to connect to vault. The vault may not exist or you may need to flush your DNS cache and try again later.
To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.
- Put any pre-requisite steps here…
az keyvault secret set --vault-name {} --name {} --value {}
Expected Behavior
Environment Summary
Linux-5.3.0-1028-azure-x86_64-with-debian-9.11
Python 3.6.5
azure-cli 2.1.0 *
Additional Context
Issue Analytics
- State:
- Created 3 years ago
- Comments:17 (7 by maintainers)
Top Results From Across the Web
ERROR: Max retries exceeded attempting to connect to vault ...
I was working on Azure Key Vault in Azure DevOps. I'm trying to retrieve the secret from Azure Key Vault from Azure DevOps...
Read more >Diagnose private links configuration issues on Azure Key Vault
In this article · Introduction · 1. Confirm that you own the client connection · 2. Confirm that the connection is approved and...
Read more >az keyvault does not list secret - Stack Overflow
I ran into the exact same error a few days ago with az keyvault secret list , and tried running the command with...
Read more >SSLError (bad handshake) when using Azure CLI - Audun Nes
When running “az keyvault secret set …” to add the secrets I was getting the following error: "Max retries exceeded with url: /<api-url>...
Read more >Use Workload identity (preview) & Secrets Store CSI Driver
Ok, let´s talk about how you can use Azure workload identity (preview) ... $location # Create secret: az keyvault secret set --vault-name ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
From my powershell ISE it is creating the secret if doesn’t exist, but in a Azure DevOps pipeline it is failing. any idea?
To reduce the confusion and narrow down on what the actual bug is please see my experience here. https://stackoverflow.com/a/71580218/495455