Fix VM publish E2E test by waiting for disk promotion - #1822
Open
anwithaun-1 wants to merge 7 commits into
Open
Conversation
anwithaun-1
force-pushed
the
topic/anwitha/fix-vm-publishrequest-flaky-test
branch
from
August 17, 2026 05:33
380bc68 to
3b5caf7
Compare
anwithaun-1
marked this pull request as ready for review
August 17, 2026 05:35
aakashchan
reviewed
Aug 18, 2026
aakashchan
reviewed
Aug 18, 2026
anwithaun-1
force-pushed
the
topic/anwitha/fix-vm-publishrequest-flaky-test
branch
from
August 19, 2026 16:08
c050857 to
a72a25c
Compare
Minimum allowed line rate is |
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
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?
Fixes a flake in the VirtualMachinePublishRequest E2E spec should preserve vAppConfig properties on a VM deployed from the published image, which timed out after waiting for Complete=True.
What does this PR do, and why is it needed?
VirtualMachinePublishRequestspecshould preserve vAppConfig properties on a VM deployed from the published imageintermittently times out waiting forComplete=TruePromoteDisks_Taskis still running. vCenter serializes the OVF capture behind that task, soUploadedstaysQueued/UploadingandCompletenever flips inside the spec's 6m budget. The neighbouring smoke publish spec is unaffected because it publishes the long-lived suite VM, whose promotion finished ~50 minutes earlier.Fix:
vmoperator.vmware.com/fast-deployannotation. Direct mode copies disks into the VM directory instead of creating a linked clone, so there are no delta disks, no promotion task, and nothing competing with the capture.bootstrap.vAppConfigsurvives publish and reappears on a VM deployed from the published image, and vApp properties live inconfig.vAppConfig, captured into the OVF envelope — disk provenance is irrelevant to it.Also re-adds
experimentalto the spec's labels, since it is being changed and has not been validated on hardware in this form.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 # vmop-4048
Are there any special notes for your reviewer:
Please add a release note if necessary: