Azure-cli: use-dev-spaces hangs and never finishes

[Lobosque]

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.

[Lobosque]

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 or this might take a long time if something is executing for more than 5 minutes.

However, I got another error just after that:

'An Azure Dev Spaces Controller' will be created that targets resource 'LobosqueAKS' in resource group 'LobosqueResourceGroup'. Continue? (y/N): y

Creating and selecting Azure Dev Spaces Controller 'LobosqueAKS' in resource group 'LobosqueResourceGroup' that targets resource 'LobosqueAKS' in resource group 'LobosqueResourceGroup'...1m 28s

Oops... An unexpected error has occurred. A report of the error will be sent to Microsoft.

I also tried enabling dev spaces through the web ui and nothing happened at all (not even an error).

[saurabsa]

Thank you for logging the bug @Lobosque
Looking into it.

[saurabsa]

@Lobosque, regarding the issue in Creating Azure Dev Spaces Controller 'LobosqueAKS', our logs show that the client is failing on your machine when it is trying to merge the cluster's kubeconfig to the default one using the command: kubectl config view --flatten
It is terminating with exit code '1' and stderr 'error: open D:\kubernetes.minikube\client.crt: The system cannot find the path specified. '.

Do you have any minikube process/cluster already running on the machine, when you are trying to run az use-dev-spaces

[saurabsa]

@Lobosque, for the first issue, can you please try downloading the installer from the direct link: http://aka.ms/get-azds-windows-az
and see how much time does is take for you?

[wterbeek]

Hi, We seem to have the same problem. We have a cluster that is dev space enabled, has http application routing enabled etc.

When i try to create a controller using the CLI everything goes alright. however, when a colleague tries to create his dev space from within visual studio 2017, he get's an error:

Starting warmup for project 'xxxxxxxxxxxxxxxxx'.
An error occurred during warmup for project 'xxxxxxxxxxxxx':
An Azure Dev Spaces controller named 'xxxxxxxxxxx' in resource group 'xxxxxxxxxxx' does not exist. This controller failed during creation with the following error:
Couldn't create DevSpacesOperationResponse`1. Please contact support.

To resolve this, delete the controller using the AZDS CLI and create a new controller to replace the failed one.

when we delete and recreate the controller, the results stay the same.

when he tries to use the following command:

az aks use-dev-spaces -g resourceGroupName -n clusterName

He gets the following error aswell:

Oops... An unexpected error has occurred. A report of the error will be sent to Microsoft.

[saurabsa]

@wterbeek about the above error "An Azure Dev Spaces controller named 'xxxxxxxxxxx' in resource group 'xxxxxxxxxxx' does not exist", are you and your colleague trying to access the same controller under different subscriptions? You would want to check if your colleague can see the controller in the list using the command "azds controller list"
If you want to share clusters/AKS, you would want to give access to your colleague's subscription by sharing the resource group that contains both AKS and DevSpaces controller.

[wterbeek]

Hi saurabh, yes we are working in the same subscription. I have owner
rights on the resource group, he has contributor rights. He is able to see
the controller using the cli.

Op wo 9 jan. 2019 22:49 schreef Saurabh Sarkar <[email protected]:

@wterbeek https://github.com/wterbeek about the above error "An Azure
Dev Spaces controller named 'xxxxxxxxxxx' in resource group 'xxxxxxxxxxx'
does not exist", are you and your colleague trying to access the same
controller under different subscriptions? You would want to check if your
colleague can see the controller in the list using the command "azds
controller list"
If you want to share clusters/AKS, you would want to give access to your
colleague's subscription by sharing the resource group that contains both
AKS and DevSpaces controller.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Azure/azure-cli/issues/8122#issuecomment-452881052,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APESuCz1ttigH8PYIIk822zuGlMk56ABks5vBmPXgaJpZM4Zf-Ik
.

[saurabsa]

@wterbeek Are you both able to run 'azds up' successfully in the controller?
When you are trying to access the controller using Visual Studio, is it the same subscription you both are logged into from different machines?

[wterbeek]

Regarding the azds up command i will check today, we are using different
machines but the same subcription. It is alsi possible the problem lies
within our aks cluster. We ate seeing some strange behavior here so i will
check it too with a new clean cluster

Op wo 9 jan. 2019 23:38 schreef Saurabh Sarkar <[email protected]:

@wterbeek https://github.com/wterbeek Are you both able to run 'azds
up' successfully in the controller?
When you are trying to access the controller using Visual Studio, is it
the same subscription you both are logged into from different machines?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Azure/azure-cli/issues/8122#issuecomment-452895854,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APESuNZCxmFuA2m___lv7j0eEE8uzMgGks5vBm9IgaJpZM4Zf-Ik
.

[saurabsa]

@wterbeek Were you able to check if the issue still persists?

[wterbeek]

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 <[email protected]:

@wterbeek https://github.com/wterbeek Were you able to check if the
issue still persists?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Azure/azure-cli/issues/8122#issuecomment-455658226,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APESuOxcfsgvV3OwybXClleJfgCgS6ezks5vEh5ugaJpZM4Zf-Ik
.

[saurabsa]

@wterbeek thank you for the confirmation

[saurabsa]

@Lobosque Were you able to check if the issue still persists?

[ryanvolum]

@saurabsa I also seem to be having the same issue - I've been running this for ~20 minutes with no update. I noticed you asked:

Do you have any minikube process/cluster already running on the machine, when you are trying to run az use-dev-spaces

I've got a minikube cluser running on my machine. Would this preclude dev spaces from installing? I'll go ahead and shut it down/update the thread with my findings.

[ryanvolum]

Update: I finally had the popup show up after about 45 minutes

[BrianRichardson]

I am experiencing hangs when using the "azds up" command which is impeding progress.
The terminal hangs at "Synchronizing files..." and have to kill the "azds.exe".
All tools are updated to the latest versions.
Failing to diagnose the cause since no errors are reported.
I have reviewed logs within %USERPROFILE%\AppData\Local\Temp\Azure Dev Spaces.

AZDS Version

Azure Dev Spaces CLI
1.0.20190715.3
API v3.2

AZ Version

azure-cli 2.0.70
command-modules-nspkg 2.0.3
core 2.0.70
nspkg 3.0.4
telemetry 1.0.3
Extensions:
dev-spaces 1.0.3
Python (Windows) 3.6.6 (v3.6.6:4cf1f54eb7, Jun 27 2018, 02:47:15) [MSC v.1900 32 bit (Intel)]
Your CLI is up-to-date.

KUBECTL Version

Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.3", GitCommit:"5e53fd6bc17c0dec8434817e69b04a25d8ae0ff0", GitTreeState:"clean", BuildDate:"2019-06-06T01:44:30Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.7", GitCommit:"4683545293d792934a7a7e12f2cc47d20b2dd01b", GitTreeState:"clean", BuildDate:"2019-06-06T01:39:30Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}

Helm Version

Client: &version.Version{SemVer:"v2.14.3", GitCommit:"0e7f3b6637f7af8fcfddb3d2941fcc7cbebb0085", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.14.1", GitCommit:"5270352a09c7e8b6e8c9593002a73535276507c0", GitTreeState:"clean"}

Docker Version

Docker version 19.03.1, build 74b1e89

[ryanjerskine]

I'm seeing this as well going through the Dev Spaces guide: https://docs.microsoft.com/en-us/azure/dev-spaces/quickstart-team-development . Going on 30min now without any feedback in the console.

[orsharon7]

Is it still normal that nothing happens?
I am facing the same issue where the installation is not responding:
Installing Dev Spaces commands... A separate window will open to guide you through the installation process.

Currently 15 minutes and nothing happens..
In case I will install it manually once, and enable devspaces from the portal, will I need to run this command again or when I will it'll recognize that azds is already installed?

Update: the installation wizard is finally opened but it is stuck on "Initializing" for 10 minutes already with no progress.. :/

[dreijer]

I'm seeing this as well going through the Dev Spaces guide: https://docs.microsoft.com/en-us/azure/dev-spaces/quickstart-team-development . Going on 30min now without any feedback in the console.

I'm seeing the same behavior as ryanjerskine simply by following the devspaces tutorial, which hangs the entire IDE when attempting to run with devspaces. I'm using VS2019 16.4.7.