Skip to content

openstack_test: trust OTE resolver exits; isolate serial coda from LB - #46

Merged
openshift-merge-bot[bot] merged 1 commit into
mainfrom
fix/openstack-test-ote-batch-trust-resolver
Oct 1, 2026
Merged

openshift-merge-bot[bot] merged 1 commit into
mainfrom
fix/openstack-test-ote-batch-trust-resolver

Conversation

@tusharjadhav3302

@tusharjadhav3302 tusharjadhav3302 commented Sep 28, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • Trust ote_resolve_results.py for OTE batch, LB serial, and serial-coda suite exit (ignore false non-zero run-test rc / Deserializaion Error / Error: N when resolved failed=0).
  • Fail when filtered list is empty (expected=0) or resolve is incomplete (resolvable!=expected / unknown>0); mark UNSTABLE for failed, unknown, or incomplete so those paths cannot silently pass.
  • Disable Machine leak-cluster serial coda on lb_tests OVN/amphora stages (coda stays on main openstack_test only) to avoid LB allowlist matcher-uniqueness false POST_FAILURE.
  • Publish serial coda under artifacts/openstack_test_serial_coda/ and test_results/openstack_tests_serial_coda/; always post batch (and coda) results when junit exists so Zuul still gets HTML/XML if a later step fails.

Test plan

  • LB stages (lb_ovn / amphora): no serial-coda splitter / matcher-uniqueness false fail; suite green when resolver failed=0
  • Main openstack_test: batch trust-resolver; false OTE rc alone does not UNSTABLE
  • Empty filtered list fails; incomplete resolve (resolvable!=expected) marks UNSTABLE (not silent green)
  • Serial coda artifacts: openstack_test_serial_coda/ + test_results/openstack_tests_serial_coda/ with XML/HTML
  • Batch openstack-test-results/ / test_results/openstack/ still published when junit exists even if coda fails later
  • Real resolver failed>0 still UNSTABLE + must-gather; junit rewrite failure still fails the suite

Comment thread collection/stages/roles/openstack_test/tasks/run_openstack_test.yml
@tusharjadhav3302 tusharjadhav3302 changed the title openstack_test: trust resolver for OTE stdin-batch exit openstack_test: OTE batch trust-resolver and disable serial coda on LB stages Sep 29, 2026
OTE run-test often exits non-zero with Deserializaion Error / Error:N
even when nested outcomes are pass/skip. Gate batch, LB serial, and
serial-coda suite results on ote_resolve_results.py counts (and fail
empty or incomplete resolve), not process rc alone. Disable Machine
leak-cluster serial coda on lb_tests OVN/amphora allowlists so uniqueness
does not false-fail. Publish coda under openstack_test_serial_coda/ and
always post batch/coda HTML/XML when junit exists; mark UNSTABLE on
failed, unknown, or resolvable!=expected.

Co-authored-by: Cursor <cursoragent@cursor.com>
@tusharjadhav3302
tusharjadhav3302 force-pushed the fix/openstack-test-ote-batch-trust-resolver branch from 6f7679c to 9ba59bf Compare September 29, 2026 18:57
@tusharjadhav3302 tusharjadhav3302 changed the title openstack_test: OTE batch trust-resolver and disable serial coda on LB stages openstack_test: trust OTE resolver exits; isolate serial coda from LB Sep 29, 2026
@tusharjadhav3302

Copy link
Copy Markdown
Contributor Author

@tusharjadhav3302 tusharjadhav3302 added the ready-for-review PR is ready for code review label Oct 1, 2026
@ekuris-redhat

Copy link
Copy Markdown
Contributor

/lgtm
/approve

@openshift-ci

openshift-ci Bot commented Oct 1, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ekuris-redhat

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci Bot added the approved label Oct 1, 2026
@openshift-merge-bot
openshift-merge-bot Bot merged commit f1f2943 into main Oct 1, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved lgtm ready-for-review PR is ready for code review

Development

Successfully merging this pull request may close these issues.

2 participants