-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[libbeat] TestKafkaPublish fails under Go 1.8 #30954
Comments
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
The failing test is the SASL/SCRAM support, and produces the infamous "client has run out of available brokers to talk to" message. I'm surprised to see that message, since most such errors after #30776 was merged (8 days ago) should give more detailed failure information -- I wonder if the source branch for the update was prior to that? If so, syncing again should give a more detailed message. In any case, it looks like a SASL/SCRAM connection failure, which could suggest a change in TLS behavior / verification in 1.18. |
I didn't look the failing tests in details, but Go 1.18 release notes mention a small change in TLS:
The default can be temporarily reverted to TLS 1.0 by setting the GODEBUG=tls10default=1 environment variable. This option will be removed in Go 1.19. I'm also already running Go 1.18 on my machine and had some python tests related to TLS failing, I didn't dig into the issue because CI was green. But I thing it might be related. |
I think the Kafka test container uses TLS 1.2, but there may be other issues e.g. it also uses the deprecated CN=hostname in its certs, if 1.18 started enforcing that deprecation then that would do it, and instances of that might turn up in the python tests too |
When running TestKafkaPublish under Go 1.18 the integration test is timing-out.
The text was updated successfully, but these errors were encountered: