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 aks command invoke failing due to API call returning broken Location
See original GitHub issueRelated command
az aks command invoke
Describe the bug
When running az aks command invoke to run any command eg kubectl get pods -A, the API returns a malformed Location on a 202 response header without the subscription id, causing crash.
Actual invoked command is run on AKS cluster.
To Reproduce
az aks command invoke --resource-group <my-rg> --name <my-aks-cluster> --command ‘kubectl get pods -A’
Expected behavior
Location header to return including Subscription ID and result of invoked command.
Environment summary
azure-cli 2.34.1 -> 2.36.0 Tested on Windows 11, Azure DevOps pipeline (Ubuntu), WSL (Ubuntu)
Additional context
Issue Analytics
- State:
- Created a year ago
- Reactions:7
- Comments:7 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
This a show-stopper P1 that breaks the mechanism to access a private AKS cluster. This bug appears to have been introduced in the Production/Live Azure REST API. @jiasli can you acknowledge that you have triaged this and are reaching out to the appropriate team, please?
Same issue here. Blocking all our CI/CD