INTEROP-9414: mpiit-data-router-reporter: add best_effort and retry logic - #83291
INTEROP-9414: mpiit-data-router-reporter: add best_effort and retry logic#83291amp-rh wants to merge 1 commit into
Conversation
The mpiit-data-router-reporter step currently has no retry logic and no best_effort flag, causing a 1-second Data Router 503 to fail an entire multi-hour CI job. This has generated 21 LPINTEROP tickets since Jan 2026 (~monthly Data Router outages). Changes: - Add best_effort: true to the ref YAML, matching medik8s-polarion-reporter - Add retry logic (5 attempts, 2-min intervals) modeled on send-results-to-reportportal - Align shell options with repo convention (set -euo pipefail, no -x) Jira: LPINTEROP-6976
openshift-ci
Bot
added
the
do-not-merge/work-in-progress
openshift-ci-robot
added
the
jira/valid-reference
|
@amp-rh: This pull request references INTEROP-9414 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "5.0.0" version, but no target version was set. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
Skipping CI for Draft Pull Request. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
WalkthroughThe Data Router reporter now uses strict shell error handling, builds launch attributes once, retries uploads up to five times, and fails after exhausting retries. The step configuration enables best-effort execution. ChangesData Router Reporter Reliability
Estimated code review effort: 2 (Simple) | ~10 minutes 🚥 Pre-merge checks | ✅ 15✅ Passed checks (15 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: amp-rh 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 |
openshift-ci
Bot
added
the
approved
|
[REHEARSALNOTIFIER]
A total of 51 jobs have been affected by this change. The above listing is non-exhaustive and limited to 25 jobs. A full list of affected jobs can be found here Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
Superseded. Reason: Superseded by #83401 (moved to amp-rh fork, applied mpitt fixes) |
3 participants
The mpiit-data-router-reporter step currently has no retry logic and no best_effort flag, causing a 1-second Data Router 503 to fail an entire multi-hour CI job. This has generated 21 LPINTEROP tickets since Jan 2026 (~monthly Data Router outages).
Changes:
Jira: INTEROP-9414
Summary by CodeRabbit
The
mpiit-data-router-reporterCI step now tolerates temporary Data Router failures. It retries uploads up to five times with two-minute intervals and enablesbest_effortexecution so brief 503 responses do not interrupt long-running OpenShift CI jobs.The script now uses repository-standard shell options and removes command tracing. It builds ReportPortal launch attributes once before the upload process.