🌱 Remove unused worker storage policy from E2E suite - #1814
Open
bryanv wants to merge 1 commit into
Open
Conversation
bryanv
force-pushed
the
bryanv/remove-e2e-worker-storagepolicy
branch
from
August 12, 2026 19:45
00a7b95 to
22337a5
Compare
This was used for VKS tests. No test ever exercised the worker-storagepolicy StorageClass as a VM or PVC storage class; it was only created and asserted into existence by its own setup path, which had already broken the suite twice on concurrent runs (BZ 3773589). Drop the config field/default, the vCenter policy helper, the namespace association plumbing, and every call site that threaded it through, and update the README's now-stale setup instructions.
bryanv
force-pushed
the
bryanv/remove-e2e-worker-storagepolicy
branch
from
August 12, 2026 19:46
22337a5 to
458ecad
Compare
Minimum allowed line rate is |
aakashchan
approved these changes
Aug 17, 2026
aruneshpa
approved these changes
Aug 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do, and why is it needed?
No test ever exercised the worker-storagepolicy StorageClass as a VM or PVC storage class; it was only created and asserted into existence by its own setup path, which had already broken the suite twice on concurrent runs (BZ 3773589). Drop the config field/default, the vCenter policy helper, the namespace association plumbing, and every call site that threaded it through, and update the README's now-stale setup instructions.
Which issue(s) is/are addressed by this PR? (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close the issue(s) when PR gets merged):Fixes #
Are there any special notes for your reviewer:
UTS smoke passed
Please add a release note if necessary: