search

microsoft / mindaro

Bridge to Kubernetes - for Visual Studio and Visual Studio Code
MIT License
307 stars 106 forks source link

Debugging is not working after Upgrading #187

Open mleitao opened 3 years ago

mleitao commented 3 years ago

Hey guys, first of all great product, I use it all the time and have grown to depend on it. I have just run into an issue when I upgraded to version 2.1.20210515.1, I was previously on 2.1.20210327.1. It seems that bridge is deploying to my pod, but my breakpoints are not being hit. bridge-library-2021-06-11-13-00-37-26536.txt bridge-mindarocli-2021-06-11-13-00-37-26536.txt

I've tried on multiple projects, and the only way I'm able to resolve is to roll back B2K to the previous version. I'm not sure what the issue is, I do see logging in my output window, and I do see that the b2k image is running.

I'm running Visual Studio Enterprise version 16.10.0 with B2K version 2.1.20210515.1

Any help would be much appreciated Thanks Mike

pragyamehta commented 3 years ago

Hi @mleitao Thanks for the appreciation! It seems like we lose the connection to our remote agent which could lead to breakpoints not being hit. Can you check if the pod running our remote agent recycles when you see this issue?

mleitao commented 3 years ago

Pragya, I think you are on to something, I don't see that the pod is recycling, here is the initial part of the log from the pod I see an entry

PortForwardConnector.Disconnect 1 AgentHub closed for 9090, id 1

Not sure what would cause that to happen as the environment has not changed between upgrading from one version to the other.

pod.log

pragyamehta commented 3 years ago

Hi @mleitao I tried debugging our todo sample app with the latest version of VS extension i.e. 2.1.20210515.1 and things seem to be working fine for me. Could you try debugging with our sample app to try to isolate where the problem may be coming from?

irperez commented 3 years ago

Hello @pragyamehta , I work with @mleitao. I can confirm that this is not isolated to him. Everyone on our team is impacted. We believe the issue is our cluster's configuration.

We are using Istio, ingx-ingress-controller, CSI Driver Secret Store (for Key Vault integration). I believe we also have Azure policy enabled. The cluster is using AAD auth.

If you need more details I can supply.

pragyamehta commented 3 years ago

@irperez Thanks for your response! Did you try debugging the sample app with Bridge to Kubernetes that I linked before in my message? Please give it a try and let me know if it works for you.