Last Update invalidate isolation....

[letmagnau]

this project seems to be belonging not affidable

i'm waiting for this bug yet.. #302

but last update of extension invalidate te essential of isolation

note that we are forcing our os in order to be B2k able to work installing a old version of icu lib ( libicu50) , without it B2k not work on manjaro

about the bug...

Describe the bug
if you configure it for isolation, it ignore the service that is being debugging --- simply redirect all the request to the main deployments

You cannot debug anymore... simply, in the hosts file will write also the service that needs to be redirect to local...

To Reproduce

simply configure it for isolation and try to debug

Expected behavior
needs to stop on brekpoint in local service

Logs
there's no error , is the behavior the problmem , it ignores the isolation

Environment Details
Client used (VS Code/Visual Studio):
1.70.1
6d9b74a70ca9c7733b29f0456fd8195364076dda
x64
Client's version:
mindaro.mindaro@1.0.120220811
Operating System:
5.18.16-1-MANJARO
Additional context
we are very sad...

[ajaffie]

We are having the same issue. I think it might be an issue with the stable tag of the routing manager image though because I am using the release of the bridge CLI that was posted here.

[dameeks]

This is a big problem for my team since we rely on isolation to debug our work. My entire team is at a standstill without it.

[hsubramanianaks]

Hi everyone apologies for the late reply, @letmagnau are you switching between isolation and non-isolation? we found an issue with switching between them, and a fix will be delivered soon. thank you for your patience.

[letmagnau]

Hi , not isolated works , but also when I'm starting from scratch in order to run in isolated mode... it not works, in other word it seems ignoring the route-as keyword
regards

[elenavillamil]

Starting from scratch with a new cluster isolation mode should work. Could you try with a newly created cluster? New release introduced a bug when switching from isolation to none isolation or viceversa. We are also releasing an update today that will fix this bug.

[letmagnau]

we constantly switch from isolate to not isolated... yes, I can do a test with a virgin cluster but we strictly need to have the availability to switch

[hsubramanianaks]

We released latest vscode extension and CLI last night can you get the latest and try? Now switching between isolated & non isolated should work, please make sure to disconnect the session while switching. Thank you.

[ajaffie]

I don't use the vscode extension, but I was able to revert the issue by editing the routing manager deployment and setting the image tag to 20220803.1 which looks like the second most recent tag.

[elenavillamil]

Hi @ajaffie, yes and new image tag 20220817.1 (latest) should work as well. It has the fix. Could you give it a try and let us know? Just in case you are running into different issue than the one discussed here.

Hi @letmagnau , could you upgrade to latest version of vscode and try again? If you dont use vscode, just switch to 20220817.1. You should be able to go back to switching between isolation and no isolation without issue (per our testing this latest version does not see the issue). I would suggest using a fresh cluster when you run with new version just in case. You may see a one time json error first time after upgrading version, but retrying works. Please let us know if it is resolved or if you still run into issues.

[ajaffie]

Thanks for the heads up @elenavillamil! I didn't see the tag 20220817.1 and it failed to pull but using latest works. For everyone else you can set the environment variable BRIDGE_ROUTINGMANAGERIMAGENAME to bridgetokubernetes.azurecr.io/routingmanager:latest to configure the extensions and CLI to use the working version. Hopefully latest does not break 😃

[elenavillamil]

@ajaffie ah sorry yes using latest or stable (bridgetokubernetes.azurecr.io/routingmanager:stable) would work. Happy it is working for you now and sorry for the inconvenience! Just as FYI you are using pretty old version of the cli (link you shared above points to July 2021 version), no worries if this is working for you, but if you run into issues in the future you may want to give latest version a try.

[ajaffie]

@elenavillamil Thanks for the link to the new version, I don't think it is posted anywhere :)
stable wasn't working for me but we might just have the old version cached in the cluster.

[elenavillamil]

@letmagnau let me know if you have an update on this. Per our testing this bug is fixed with new version. I will probably close this in the next couple days if I have not heard back. Feel free to re-open if the issue is not fixed for you.

[letmagnau]

hi @elenavillamil

I tried to update at latest version of B2K ext and without recreate the cluster ( it's very annoying for us) not working yet
Behavior seems to be the same.
I will try with a new fresh cluster, but if you could tell me if there are fix that I will run on old cluster in order to purge it ?

regards