Repository navigation
test(kafka): wait for ZooKeeper PVC deletion - #4484
Aleksei Sviridkin (lexfrei) merged 1 commit into
Conversation
Negative PVC assertions can stop on an API read error before the deletion timeout expires. Signed-off-by: Yan Bondarenko <[email protected]>
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository: cozystack/cozystack/.coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
github-actions
Bot
added
area/database
a977a6b
into
release-1.6
2 participants
This reopens a fork pull request from a branch in this repository so its CI can run. The commit is the one from #4481 by europrinter (@yankawai), unchanged. On release-1.6 the pull-request CI pushes the images it builds, and a run from a fork has no registry credentials, so #4481 could never get past the build jobs to e2e. The description below is the author's.
What this PR does
Wait for both ZooKeeper PVCs to disappear after Kafka deletion. Negative assertions can stop on an API read error before their timeout; deletion watches wait for the resource to be removed. The existing Bound and KafkaTopic checks are unchanged.
Carries the test-only change from c92828c in #4339, which was not included in #4402. This targets
release-1.6; the Kafka suite onmainuses KRaft without ZooKeeper.Validated with Chainsaw 0.2.15: delayed deletion, an already absent PVC, an interrupted watch, and the read-error fixture pass. A retained PVC and forbidden access fail. The full Kafka E2E run remains for CI.
Screenshots
Not applicable.
Downstream repositories
Release note