Repository navigation
e2e: assert sync status, conditions, and cleanup - #2194
Open
JohnStrunk wants to merge 3 commits into
Open
JohnStrunk wants to merge 3 commits into
JohnStrunk wants to merge 3 commits into
Conversation
Contributor
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JohnStrunk The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Add a shared role for status, condition, latest-image, and per-CR temporary-resource checks. Integrate it into all CR-based e2e playbooks and add a no-mover error case. Signed-off-by: John Strunk <jstrunk@redhat.com> Co-authored-by: OpenCode - GPT-6 Luna <noreply@opencode.ai>
Regenerate the upstream and downstream scorecard configs to include the new validation-error playbook. Signed-off-by: John Strunk <jstrunk@redhat.com> Co-authored-by: OpenCode - GPT-6 Luna <noreply@opencode.ai>
Pass the actual ReplicationDestination name to the shared status role. Signed-off-by: John Strunk <jstrunk@redhat.com> Co-authored-by: OpenCode - GPT-6 Luna <noreply@opencode.ai>
JohnStrunk
force-pushed
the
opencode/issue-2188-e2e-sync-status-assertions
branch
from
October 28, 2026 19:42
636431d to
e0091f4
Compare
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2194 +/- ##
=====================================
Coverage 68.4% 68.5%
=====================================
Files 61 61
Lines 6213 6217 +4
=====================================
+ Hits 4255 4259 +4
Misses 1636 1636
Partials 322 322
🚀 New features to boost your workflow:
|
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.



Summary
Fixes #2188. Adds shared end-to-end assertions for VolSync synchronization status, conditions, and temporary-resource cleanup.
roles/verify_sync_statuswith completion, continuous, and validation-error modes.Synchronizing=False, reasonError, and the expected validation message.Walkthrough
The shared role checks settled
WaitingForManual/WaitingForSchedulesuccess, mover result, timing and schedule status, latest-image existence, and cleanup-labeled PVCs, VolumeSnapshots, Jobs, and Pods. Continuous mode handles always-on Syncthing and untriggered movers without falsely requiring an idle state. Error mode covers a validation failure before a mover starts.Showboat walkthrough and repeatable syntax-check evidence
Demo: Not applicable; this is test infrastructure and adds no user-facing runtime feature. No live e2e was run because the playbooks require a disposable Kubernetes cluster.
Verification
test_*.ymlplaybooks.status.observedGenerationto prove completion without a fixed, flaky sleep; existing controller tests cover reconcile idempotence.(AI generated)