Skip to content
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

Mitigate Failed to acquire idempotence PID error from test run report #603

Closed
1 of 2 tasks
acn-sbuad opened this issue Aug 22, 2024 · 0 comments
Closed
1 of 2 tasks
Assignees
Labels
kind/bug Something isn't working kind/chore Non functional, often repeating tasks. status/draft Status: When you create an issue before you have enough info to properly describe the issue.

Comments

@acn-sbuad
Copy link
Contributor

acn-sbuad commented Aug 22, 2024

Description

Remaining work from #594.
The error was identified, but what remains is to find a way to either fix the error so the message is never logged or ensuring the log message does not result in the rest result being evaluated to false.

Additional Information

The error comes from the kafka-broker. The coordinator load is still in progress.
This is expected behaviour when starting/restarting the broker.

Tasks

  • Add delay to ensure Kafka is running properly before pushing messages

Acceptance Criterias

  • Workflow runs without error
@acn-sbuad acn-sbuad added status/draft Status: When you create an issue before you have enough info to properly describe the issue. kind/chore Non functional, often repeating tasks. labels Aug 22, 2024
@olebhansen olebhansen added the kind/bug Something isn't working label Aug 26, 2024
@tba76 tba76 self-assigned this Sep 18, 2024
@tba76 tba76 closed this as completed Oct 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working kind/chore Non functional, often repeating tasks. status/draft Status: When you create an issue before you have enough info to properly describe the issue.
Projects
None yet
Development

No branches or pull requests

4 participants