You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For some reason the kuttl test redpanda-schema-registry-sasl has started to fail. 1
Kuttl is reporting a failure on step 5:
resource Job:redpanda-system/create-schema-with-tls-rp-sasl: .status.conditions: key is missing from map
Pod/Job logs are reporting that a connections to the schema registry is failing:
2024-07-16T19:57:18.182195185Z stderr F * Trying 10.96.121.10:8081...
2024-07-16T19:57:18.182223518Z stderr F * connect to 10.96.121.10 port 8081 failed: Connection refused
2024-07-16T19:57:18.182226921Z stderr F * Failed to connect to schema-registry-sasl-cluster.redpanda-system.svc.cluster.local. port 8081 after 0 ms: Couldn't connect to server
2024-07-16T19:57:18.182235919Z stderr F * Closing connection 0
2024-07-16T19:57:57.942166266Z stderr F * Trying 10.96.121.10:8081...
2024-07-16T19:57:57.942264788Z stderr F * Connected to schema-registry-sasl-cluster.redpanda-system.svc.cluster.local. (10.96.121.10) port 8081 (#0)
2024-07-16T19:57:57.944063748Z stderr F * ALPN: offers h2,http/1.1
2024-07-16T19:57:57.944159743Z stderr F } [5 bytes data]
2024-07-16T19:57:57.944173437Z stderr F * TLSv1.3 (OUT), TLS handshake, Client hello (1):
2024-07-16T19:57:57.94417901Z stderr F } [512 bytes data]
2024-07-16T19:57:57.944680686Z stderr F * CAfile: /etc/tls/certs/schema-registry/ca.crt
2024-07-16T19:57:57.944683927Z stderr F * CApath: /etc/ssl/certs
2024-07-16T19:57:57.944705628Z stderr F { [5 bytes data]
2024-07-16T19:57:57.944719775Z stderr F * OpenSSL/3.0.11: error:0A00010B:SSL routines::wrong version number
2024-07-16T19:57:57.944724333Z stderr F * Closing connection 0
Notably, it seems that neither the Pod nor the Service expose port 8081.
Huh... So it seems that this might just be general flakiness in/of the kuttl suite? The most recent run passed and a quick glance at the history indicates that it's not always redpanda-schema-registry-sasl that fails.
For some reason the kuttl test
redpanda-schema-registry-sasl
has started to fail. 1Kuttl is reporting a failure on step 5:
Pod/Job logs are reporting that a connections to the schema registry is failing:
Notably, it seems that neither the Pod nor the Service expose port 8081.
JIRA Link: K8S-302
The text was updated successfully, but these errors were encountered: