azure-cli: use-dev-spaces hangs and never finishes
Describe the bug
use-dev-spaces
command hangs and never finishes, the only output (even with --verbose
flag) is:
Installing Dev Spaces (Preview) commands...
A separate window will open to guide you through the installation process.
I could try enabling this elsewehere (azure web UI for example) but it looks like running this command is the only way to install azds
.
To Reproduce Follow the Get Started on Azure Dev Spaces with .NET Core guide until you reach the step where you run the command
az aks use-dev-spaces -g MyResourceGroup -n MyAKS
Expected behavior The command should run thoroughly or at least give an error message as to why it is not completing.
Environment summary
- Azure cli version: 2.0.53
- .net core SDK: 2.2
- OS: Windows 10
- shell: PowerShell
Additional context
I have tried to go through the guide using two different Azure regions, and both gave me the same result.
It is my first time using Azure and I noticed some commands take a long time to finish, so I waited for around 10 minutes on 1st try before closing and 20 minutes on the second.
I also tried to run the command using cmd.exe
and got the same behaviour.
About this issue
- Original URL
- State: open
- Created 6 years ago
- Reactions: 5
- Comments: 19 (8 by maintainers)
Update: I finally had the popup show up after about 45 minutes
Hi saurabh,
Actually we had some more problems with the cluster so we deleted it and recreated it. After that we noticed that a contracter had created different network security groups that conflicted with the cluster. I am confident that we will get the dev spaces soon.
Thank you for your time and patience, if we need more support i will get back to you
Op vr 18 jan. 2019 20:20 schreef Saurabh Sarkar <notifications@github.com:
On my third try, after about 30 minutes, I was prompted with a GUI to install
azds
and continue. An important feedback here from UX perspective is to show some kind of progress orthis might take a long time
if something is executing for more than 5 minutes.However, I got another error just after that:
I also tried enabling dev spaces through the web ui and nothing happened at all (not even an error).