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

rptest: clean up cluster metadata in CDT #15754

Merged
merged 1 commit into from
Dec 19, 2023

Conversation

andrwng
Copy link
Contributor

@andrwng andrwng commented Dec 19, 2023

In CDT we examine each bucket hash and use that to determine the list of objects to delete. This wasn't taking into account the new cluster metadata prefix. The result is that we would not completely empty the bucket before attempting to delete it, resulting in a failed bucket deletion.

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.3.x
  • v23.2.x
  • v23.1.x

Release Notes

  • none

In CDT we examine each bucket hash and use that to determine the list of
objects to delete. This wasn't taking into account the new cluster
metadata prefix. The result is that we would not completely empty the
bucket before attempting to delete it, resulting in a failed bucket
deletion.
andrwng added a commit to andrwng/redpanda that referenced this pull request Dec 19, 2023
In general this seems like an unexpected case. Perhaps it's sometimes an
S3 issue, but it's certainly possible this is caused by a ducktape bug
(see redpanda-data#15754).

In either case, it seems worthwhile to flag, if anything, to inform us
when to expect artifacts to show up in our S3 account.
@andrwng andrwng merged commit 212c308 into redpanda-data:dev Dec 19, 2023
18 checks passed
@vbotbuildovich
Copy link
Collaborator

/backport v23.3.x

vbotbuildovich pushed a commit to vbotbuildovich/redpanda that referenced this pull request Dec 22, 2023
In general this seems like an unexpected case. Perhaps it's sometimes an
S3 issue, but it's certainly possible this is caused by a ducktape bug
(see redpanda-data#15754).

In either case, it seems worthwhile to flag, if anything, to inform us
when to expect artifacts to show up in our S3 account.

(cherry picked from commit a99074c)
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.

None yet

3 participants