Skip to content

ROSAENG-64505: strip junit output for rosa-hcp-external-auth-f3 - #83059

Open
amandahla wants to merge 1 commit into
openshift:mainfrom
amandahla:ROSAENG-64505-strip-junit-external-auth
Open

ROSAENG-64505: strip junit output for rosa-hcp-external-auth-f3#83059
amandahla wants to merge 1 commit into
openshift:mainfrom
amandahla:ROSAENG-64505-strip-junit-external-auth

Conversation

@amandahla

@amandahla amandahla commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Summary

Enable STRIP_JUNIT_OUTPUT for rosa-hcp-external-auth-f3 so Prow sidecar censoring does not replace day2 JUnit XML and fail send-results-to-reportportal / droute send.

Extends the same pattern introduced in #82252 (8fbeb4865d1).

Changes

  • Wire STRIP_JUNIT_OUTPUT into fullcycle runtime refs/scripts (day1-post, day2, destructive, destroy, destroy-post) using the same strip-before-cp logic as rosa-tests-commands.sh
  • Set STRIP_JUNIT_OUTPUT: "true" on rosa-hcp-external-auth-f3

Related

Test plan

  • make update
  • make ci-operator-checkconfig
  • /pj-rehearse rosa-hcp-external-auth-f3 (or ack/skip after review)
  • Confirm subsequent periodic run keeps day2 JUnit XML intact and ReportPortal upload succeeds

Made with Cursor

Summary by CodeRabbit

This PR updates ROSA HCP external-auth CI runs to prevent Prow sidecar censoring from corrupting day2 JUnit XML.

  • Enables STRIP_JUNIT_OUTPUT=true for rosa-hcp-external-auth-f3.
  • Adds the variable to day1-post, day2, destructive, destroy, and destroy-post runtime steps.
  • When enabled, each step removes system-out and system-err elements before copying JUnit results to artifacts.
  • Helps prevent send-results-to-reportportal and droute send failures.
  • make update and make ci-operator-checkconfig completed. Rehearsal and periodic-run validation remain pending.

Extend STRIP_JUNIT_OUTPUT from openshift#82252 to fullcycle runtime steps and
enable it for rosa-hcp-external-auth-f3 so sidecar censoring does not
replace day2 junit XML and break send-results-to-reportportal.

Signed-off-by: Amanda Hager Lopes de Andrade Katz <amanda.katz@redhat.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
@openshift-ci-robot

openshift-ci-robot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

@amandahla: This pull request references ROSAENG-64505 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 sub-task to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Summary

Enable STRIP_JUNIT_OUTPUT for rosa-hcp-external-auth-f3 so Prow sidecar censoring does not replace day2 JUnit XML and fail send-results-to-reportportal / droute send.

Extends the same pattern introduced in #82252 (8fbeb4865d1).

Changes

  • Wire STRIP_JUNIT_OUTPUT into fullcycle runtime refs/scripts (day1-post, day2, destructive, destroy, destroy-post) using the same strip-before-cp logic as rosa-tests-commands.sh
  • Set STRIP_JUNIT_OUTPUT: "true" on rosa-hcp-external-auth-f3

Related

Test plan

  • make update
  • make ci-operator-checkconfig
  • /pj-rehearse rosa-hcp-external-auth-f3 (or ack/skip after review)
  • Confirm subsequent periodic run keeps day2 JUnit XML intact and ReportPortal upload succeeds

Made with Cursor

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.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 6, 2026
@openshift-ci

openshift-ci Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: amandahla

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 Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 6, 2026
@coderabbitai

coderabbitai Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Walkthrough

ROSA runtime steps now support optional removal of system-out and system-err elements from JUnit XML reports before artifact upload. The external-auth test enables this behavior.

Changes

ROSA JUnit output handling

Layer / File(s) Summary
JUnit output configuration
ci-operator/step-registry/rosa/tests/runtime/*/*-ref.yaml, ci-operator/config/openshift/rosa/openshift-rosa-master__e2e.yaml
Runtime references define STRIP_JUNIT_OUTPUT as false by default. The external-auth test sets it to true.
JUnit report sanitization
ci-operator/step-registry/rosa/tests/runtime/*/*-commands.sh
When enabled, runtime scripts use Python to remove system-out and system-err elements before artifact upload.

Estimated code review effort: 2 (Simple) | ~10 minutes

Suggested reviewers: jerichokeyne

🚥 Pre-merge checks | ✅ 15
✅ Passed checks (15 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly identifies the main change: enabling JUnit output stripping for the specified ROSA test.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed The PR changes only CI YAML and shell scripts; no Ginkgo test titles or dynamic title construction were added or modified.
Test Structure And Quality ✅ Passed The PR changes only shell scripts and YAML files; no Ginkgo test code, It blocks, or Ginkgo constructs are present, so this check is not applicable.
Microshift Test Compatibility ✅ Passed The commit changes only CI YAML and shell files; it adds no Ginkgo tests or test declarations requiring MicroShift compatibility review.
Single Node Openshift (Sno) Test Compatibility ✅ Passed The PR changes only YAML and shell CI runtime files; it adds no Ginkgo e2e tests or test declarations that could assume a multi-node cluster.
Topology-Aware Scheduling Compatibility ✅ Passed The PR changes only CI job YAML, runtime reference YAML, and shell scripts; the parent-to-HEAD diff adds no scheduling constraints or deployment/operator/controller code.
Ote Binary Stdout Contract ✅ Passed The PR changes only YAML and shell JUnit handling; no Go files or added OTE entry points or stdout APIs such as main, RunSpecs, fmt, klog, or os.Stdout were found.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed The pull request adds no Ginkgo e2e tests. It changes only CI configuration, shell scripts, and YAML references for JUnit output handling.
No-Weak-Crypto ✅ Passed The exact patch scan found no MD5, SHA1, DES, RC4, Blowfish, ECB, crypto API, custom crypto, or secret/token comparison usage; only a feature-flag equality check was added.
Container-Privileges ✅ Passed The diff adds only STRIP_JUNIT_OUTPUT wiring and XML cleanup; changed manifests and runtime refs contain no privileged, host*, SYS_ADMIN, allowPrivilegeEscalation, capability, or root settings.
No-Sensitive-Data-In-Logs ✅ Passed Added code logs only a fixed JUnit-stripping message and does not print tokens or XML content; OCM_TOKEN handling and command logging were pre-existing.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@amandahla

Copy link
Copy Markdown
Contributor Author

/pj-rehearse rosa-hcp-external-auth-f3

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@amandahla: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@amandahla: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
periodic-ci-openshift-rosa-master-e2e-rosa-sts-shared-vpc-f3 N/A periodic Registry content changed
periodic-ci-openshift-rosa-master-e2e-rosa-sts-private-link-f3 N/A periodic Registry content changed
periodic-ci-openshift-rosa-master-e2e-rosa-hcp-private-link-f3 N/A periodic Registry content changed
periodic-ci-openshift-rosa-master-e2e-rosa-sts-advanced-f3 N/A periodic Registry content changed
periodic-ci-openshift-rosa-master-e2e-rosa-hcp-shared-vpc-f3 N/A periodic Registry content changed
periodic-ci-openshift-rosa-master-e2e-rosa-hcp-advanced-f3 N/A periodic Registry content changed
periodic-ci-openshift-rosa-master-e2e-rosa-hcp-arm-f7 N/A periodic Registry content changed
periodic-ci-openshift-rosa-master-e2e-rosa-hcp-external-auth-f3 N/A periodic Ci-operator config changed
periodic-ci-openshift-rosa-master-e2e-rosa-hcp-advanced-regional-f3 N/A periodic Registry content changed
periodic-ci-openshift-rosa-master-e2e-rosa-non-sts-advanced-critical-high-f3 N/A periodic Registry content changed

Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
ci-operator/config/openshift/rosa/openshift-rosa-master__e2e.yaml (1)

154-154: 🗄️ Data Integrity & Integration | 🔵 Trivial

Run the pending runtime rehearsal before merge.

Verify that rosa-hcp-external-auth-f3 uploads parseable JUnit XML and that send-results-to-reportportal or droute send succeeds.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@ci-operator/config/openshift/rosa/openshift-rosa-master__e2e.yaml` at line
154, Run the pending runtime rehearsal before merging: verify that
rosa-hcp-external-auth-f3 produces parseable JUnit XML with STRIP_JUNIT_OUTPUT
enabled, then confirm send-results-to-reportportal or droute send completes
successfully.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@ci-operator/config/openshift/rosa/openshift-rosa-master__e2e.yaml`:
- Line 154: Run the pending runtime rehearsal before merging: verify that
rosa-hcp-external-auth-f3 produces parseable JUnit XML with STRIP_JUNIT_OUTPUT
enabled, then confirm send-results-to-reportportal or droute send completes
successfully.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: 1f1ee850-6c76-4f1b-9ac1-5aaf9691c482

📥 Commits

Reviewing files that changed from the base of the PR and between 6085899 and f246a96.

📒 Files selected for processing (11)
  • ci-operator/config/openshift/rosa/openshift-rosa-master__e2e.yaml
  • ci-operator/step-registry/rosa/tests/runtime/day1-post/rosa-tests-runtime-day1-post-commands.sh
  • ci-operator/step-registry/rosa/tests/runtime/day1-post/rosa-tests-runtime-day1-post-ref.yaml
  • ci-operator/step-registry/rosa/tests/runtime/day2/rosa-tests-runtime-day2-commands.sh
  • ci-operator/step-registry/rosa/tests/runtime/day2/rosa-tests-runtime-day2-ref.yaml
  • ci-operator/step-registry/rosa/tests/runtime/destroy-post/rosa-tests-runtime-destroy-post-commands.sh
  • ci-operator/step-registry/rosa/tests/runtime/destroy-post/rosa-tests-runtime-destroy-post-ref.yaml
  • ci-operator/step-registry/rosa/tests/runtime/destroy/rosa-tests-runtime-destroy-commands.sh
  • ci-operator/step-registry/rosa/tests/runtime/destroy/rosa-tests-runtime-destroy-ref.yaml
  • ci-operator/step-registry/rosa/tests/runtime/destructive/rosa-tests-runtime-destructive-commands.sh
  • ci-operator/step-registry/rosa/tests/runtime/destructive/rosa-tests-runtime-destructive-ref.yaml

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@amandahla: job(s): rosa-hcp-external-auth-f3 either don't exist or were not found to be affected, and cannot be rehearsed

@amandahla

Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-rosa-master-e2e-rosa-hcp-external-auth-f3

@amandahla

Copy link
Copy Markdown
Contributor Author

/pj-rehearse --pull=openshift/rosa#3454 periodic-ci-openshift-rosa-master-e2e-rosa-hcp-upgrade-y-stream-f3

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@amandahla: your /pj-rehearse request was not processed because the request waited in queue for longer than 5 minutes. Please retry in a few minutes.

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@amandahla: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

1 similar comment
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@amandahla: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@amandahla: job(s): --pull=openshift/rosa#3454, periodic-ci-openshift-rosa-master-e2e-rosa-hcp-upgrade-y-stream-f3 either don't exist or were not found to be affected, and cannot be rehearsed

@openshift-ci

openshift-ci Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

@amandahla: all tests passed!

Full PR test history. Your PR dashboard.

Details

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 kubernetes-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants