search

MicrosoftDocs / azure-docs

Open source documentation of Microsoft Azure
https://docs.microsoft.com/azure
Creative Commons Attribution 4.0 International
10.21k stars 21.37k forks source link

debugging error. #9459

Closed junpark12 closed 6 years ago

junpark12 commented 6 years ago

Hi when i run debug , i received the following exception.

Microsoft Visual Studio

Could not find Azure Dev Spaces resource 'xxxx' in resource group 'xxxx' in subscription 'xxxxxxx'.

It worked before, but when i try "debug across multiple services" section, i receive the sample error from webfrontend and webapi projects.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

mike-urnun-msft commented 6 years ago

@junpark12 Thank you for your feedback! We will investigate and get back to you with our findings.

junpark12 commented 6 years ago

When i create new space then access "spacename.s" site, i receive "503" error from nginx ingress controller. The error originated from newly created pod and it says "unable to prepare context: unable to evaluate symlinks in Dockerfile path: lstat /source/webfrontend/Dockerfile.develop: no such file or directory

_MINDARO_BUILDISSUCCESS#false"

mike-urnun-msft commented 6 years ago

Hey @junpark12 - Sorry for delay in response here, I will be looking into this today and share my findings. Stay tuned!

mike-urnun-msft commented 6 years ago

Hey @junpark12 - I went through the steps and reproduced same error: 503 from nginx. I was able to overcome this error and other issues by deleting the problematic service from the Kubernetes Dashboard and re-running the deployment.

Here are the steps i took:

  1. Installed kubectl to my azure cli This can be found from Azure Portal -> Kubernetes Services -> Your Existing AKS -> Overview tab and you'll find "View Kubernetes dashboard" which will open a blade with necessary details to install kubectl
  2. Open Kubernetes Dashboard, go to Services tab, and delete the problematic service from your first deployment. It'd be named webfrontend as per this documentation.
  3. Go back to Visual Studio and re-run the deployment/debugging by hitting F5 or pressing the "Azure Dev Space" button: image
  4. Viola! You should be seeing complete debugging experience in your Visual Studio against your Kubernetes cluster on Azure. Go to the webapp URL on your browser and click the About link to see the code execution halt at the breakpoint in Visual Studio as per this documentation.

We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and tag me in your reply and we will gladly continue the discussion.