ccl/sqlproxyccl: TestProxyProtocol failed

[cockroach-teamcity]

ccl/sqlproxyccl.TestProxyProtocol failed with artifacts on release-24.3 @ 59710ae3d1105bca768e4d340c797a40419a5e27:

=== RUN   TestProxyProtocol
    test_log_scope.go:165: test logs captured to: /artifacts/tmp/_tmp/2dcdeaae7bc06474bb2d1d585750c46b/logTestProxyProtocol3999454132
    test_log_scope.go:76: use -show-logs to present logs inline
    test_server_shim.go:152: automatically injected an external process virtual cluster under test; see comment at top of test_server_shim.go for details.
    proxy_handler_test.go:230: B
    proxy_handler_test.go:249: 
        	Error Trace:	github.com/cockroachdb/cockroach/pkg/ccl/sqlproxyccl/proxy_handler_test.go:2939
        	Error:      	Expected nil, but got: &sqlproxyccl.errWithCode{
        	            	    code:  4,
        	            	    cause: &withstack.withStack{
        	            	        cause: &errutil.withPrefix{
        	            	            cause:  &errors.errorString{s:"proxyproto: proxy protocol signature not present"},
        	            	            prefix: "while receiving startup message",
        	            	        },
        	            	        stack: &withstack.stack{0x431d801, 0x432936c, 0x432ee48, 0x1243548, 0x48ec14},
        	            	    },
        	            	}
        	Test:       	TestProxyProtocol
    panic.go:626: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/2dcdeaae7bc06474bb2d1d585750c46b/logTestProxyProtocol3999454132
--- FAIL: TestProxyProtocol (4.56s)
=== RUN   TestProxyProtocol/server_requires_proxy_protocol
    testing.go:1576: test executed panic(nil) or runtime.Goexit: subtest may have called FailNow on a parent test
    --- FAIL: TestProxyProtocol/server_requires_proxy_protocol (0.03s)

Help

See also: How To Investigate a Go Test Failure (internal)

/cc @cockroachdb/sql-foundations @cockroachdb/server

This test on roachdash | Improve this report!

Jira issue: CRDB-43501

[github-actions]

We have marked this issue as stale because it has been inactive for
12 months. If this issue is still relevant, removing the stale label
or adding a comment will keep it active. Otherwise, we'll close it in
10 days to keep the issue queue tidy.