RoutingManager fails with Null ref in AddLoadBalancerTriggersAsync' about dev-spaces

[pragyamehta]

Hi @ghostcoach We are releasing the fix tomorrow. Thanks for your patience :)

[amsoedal]

Thanks so much for reporting this @catnip-se! We'll investigate and let you know as soon as the fix is available.

[catnip-se]

Some more information.
I have tested on a different cluster (without any ingresses) and even though no exception is thrown in the RoutingManager there the problem with getting the routing manager deployment status from Visual Studio remains.

[amsoedal]

@catnip-se, can you attach the routing manager log for the second issue you're seeing?

[catnip-se]

Sure, here it is.
routingmanager.log
bridge-library-2021-01-05-14-49-58-22788.txt

In this case it seems to be some timeout problem in VS. If I made a second attempt to connect from VS after the routing manager had completed the startup it was possible to start the debugging pods in this cluster.

[pragyamehta]

Hi @catnip-se According to the logs you sent last, It seems as though the envoy pods we start in your cluster for debugging were not able to come up in time. This could be something intermittent with your kube-api, but if you see this consistently, please check if you have enough space on your cluster to spin up these additional pods for setting up debugging. Thanks!

As for the nullref you are seeing, we have fixed it. It will be rolled sometime next week to production.
Thanks for reporting these issues and do let us know if you see more in the future. Cheers!

[ghostcoach]

@pragyamehta Do you have an ETA on the fix for the nullref error? Looking forward to this fix :)