Easwar Swaminathan
Easwar Swaminathan
Currently in the `xds_server_serving_mode_test.go`, we create the xDS enabled gRPC server and start serving. Only after that do we push the server side resources to the management server. And in...
Technically it should. But we don't see it here. Maybe some bug in the go-control-plane.
Keeping this open as #4406 is more of a workaround.
Another failed run: https://github.com/grpc/grpc-go/pull/4443/checks?check_run_id=2604062853
Complete paste of the failing test's log to avoid the extra step of retrieving it from GA. ``` --- FAIL: Test (12.37s) --- FAIL: Test/ServerSideXDS_ServingModeChanges (10.07s) tlogger.go:99: server.go:111 [xds] [xds-server...
The above also seems to be a result of https://github.com/envoyproxy/go-control-plane/issues/431. It is a little unclear to me though as to why we eventually see those resources from the server after...
One more: https://github.com/grpc/grpc-go/pull/4582/checks?check_run_id=3011929638
I think the problem could be as follows: Two listener resources are added to the management server, update is received by the gRPC server, both listeners move to `serving` mode....
Should be fixed by https://github.com/grpc/grpc-go/pull/4689.
Another: https://github.com/grpc/grpc-go/pull/4718/checks?check_run_id=3468030691