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

Fix for delete-records tests that don't handle RpkExceptions #11963

Merged

Conversation

graphcareful
Copy link
Contributor

PR #11957 introduced a behavior change in how rpk topic trim handles on observed errors. It now returns a processes exit code of 1 if there is any failure detected. This change is making the ducktape Rpk client throw on errors which is making some tests that expect failures actually fail.

This PR also includes a fix for another error which was making the read replica delete records test fail. That test invoked KCL::DeleteRecords which was deprecated without updating that test to use the Rpk tools version of the same command.

Backports Required

  • none - not a bug fix
  • none - this is a backport
  • none - issue does not exist in previous branches
  • none - papercut/not impactful enough to backport
  • v23.1.x
  • v22.3.x
  • v22.2.x

Release Notes

  • none

- Now that trim_prefix throws if any topic trim results in any error,
rpktool will throw

- Tests that assert on a particular error must account for this

- Fixes: redpanda-data#11961
andrwng
andrwng previously approved these changes Jul 8, 2023
- In a previous commit KCL::delete_records was depricated in favor of
RpkTools but the update was never made to the invocation of the call in
the read_replica and shadow indexing suites
@piyushredpanda
Copy link
Contributor

Known CI Failures: #11842

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants