-
Notifications
You must be signed in to change notification settings - Fork 593
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
CI Failure (RpkException - SASL authentication failed) in SchemaRegistryAutoAuthTest.test_schema_id_validation
#11203
Comments
similar errors from another testcase: |
May be related to #11141 |
Similar errors exist in |
So I sync'd with @BenPope and we both agreed that this failure is not happening because of a problem with AutoAuth or ephemeral credentials. Instead, this problem is happening because of a timing issue between RedpandaService auto-creating the admin user and RPK issuing a CreateTopic request. I continued the investigation to see if using a different client to create topics solves the problem, so I tried using KafkaCliTools. I continued my experiments by forcing the RpkTool to retry on SASL_AUTHENTICATION_FAILED. The result was that all test runs passed. This tells me that our RpkTool may be issuing a CreateTopics request before the admin user finishes replicating to other nodes or something like that. Nevertheless, this seems like a test issue. Therefore, I am assigning |
In tests that enable SASL auth, it is possible for RPK to issue a CreateTopics requests before the user has replicated across the cluster. The solution is to retry the request. Fixes redpanda-data#11203
https://buildkite.com/redpanda/vtools/builds/7916#0188856f-e4e9-4ee3-944e-95a01dd43a36
The text was updated successfully, but these errors were encountered: