Skip to content

INTEROP-9417: Add acm-tests-clc-smoke step for reduced CLC scope - #83359

Open
amp-rh wants to merge 4 commits into
openshift:mainfrom
amp-rh:interop-9417-clc-smoke
Open

INTEROP-9417: Add acm-tests-clc-smoke step for reduced CLC scope#83359
amp-rh wants to merge 4 commits into
openshift:mainfrom
amp-rh:interop-9417-clc-smoke

Conversation

@amp-rh

@amp-rh amp-rh commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

Summary

Adds acm-tests-clc-smoke, a right-sized variant of acm-tests-clc-create for OPP interop jobs.

Problem: acm-tests-clc-create has a 28800s (8h) timeout and suppresses all failures with || :, even though it only creates 1 AWS managed cluster in ~50 minutes. When CLC fails silently, downstream steps (acm-fetch-managed-clusters, acm-opp-app) run against a missing cluster and produce confusing failures.

Solution: New step with behavioral differences:

Property acm-tests-clc-create acm-tests-clc-smoke
Timeout 28800s (8h) 5400s (90 min)
Failure handling || : (always passes) Propagates errors (exit code captured, reports always collected)
Xtrace discipline Leaks cluster endpoints Tracing disabled through all sensitive assignments
Credential validation Silent exit on missing creds Explicit error message on extraction failure
Secret handling AWS key in process args jq --rawfile keeps secret off cmdline

Reviewer Guide

Start here: acm-tests-clc-smoke-ref.yaml shows the step definition (timeout, credentials, env vars).

Core behavioral changes in acm-tests-clc-smoke-commands.sh vs acm-tests-clc-create:

  1. Failure propagation with report preservation: Exit code captured via || clcStatus=$? so reports are always copied to ARTIFACT_DIR before propagating the failure.
  2. Xtrace discipline: Tracing stays disabled (set +x) from password extraction through test execution, preventing cluster endpoint URLs from appearing in CI logs.
  3. Credential validation: Explicit error message (echo "ERROR: ..." 1>&2; exit 1) instead of silent [ -n ] && [ -n ] that exits with no diagnostic.
  4. Secret handling: AWS secret key passed via jq --rawfile to keep it off the process argument list.

Config changes (2 files, 1-line each): swap acm-tests-clc-createacm-tests-clc-smoke in the test section. The acm-tests-clc-destroy post step is unchanged.

Risk: If CLC has transient failures that the || : was masking, this step will now fail the job. That's intentional (fail fast so we triage the real issue instead of debugging missing-cluster errors in downstream steps). The 90-min timeout provides ~80% headroom over the observed ~50 min average.

Changes

  • New step acm-tests-clc-smoke under ci-operator/step-registry/acm/tests/clc-smoke/
  • OPP configs (ocp4.22, ocp5.0) updated to use the new step
  • acm-tests-clc-destroy post step unchanged

Test Plan

  • Rehearsal passes with new step
  • Downstream acm-fetch-managed-clusters and acm-opp-app succeed
  • Step completes in under 90 minutes
  • CLC failure correctly propagates (no silent pass-through)

/cc @dtthuynh @vboulos

Rehearsal validation

Steps in this PR: acm-tests-clc-smoke (new step)

This step is not included in the batch PR (#83405). It was rehearsed independently via opp-aws-4.22. The rehearsal failed at an infrastructure level unrelated to this step. Structural CI checks pass, and the step script follows established patterns from the existing acm-tests-clc-create step.

Rehearsal ack rationale: All rehearsal failures are caused by known infrastructure issues (ACS upstream scanner timeout, ACM S3 credential rotation) unrelated to this PR's changes. All structural CI checks (ci-operator-config, ci-operator-registry, step-registry-shellcheck, yamllint, generated-config) pass. See batch PR #83405 for full rehearsal results and analysis.

@openshift-ci
openshift-ci Bot requested a review from dtthuynh August 12, 2026 20:40
@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 12, 2026
@openshift-ci
openshift-ci Bot requested a review from vboulos August 12, 2026 20:40
@openshift-ci-robot

openshift-ci-robot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

@amp-rh: This pull request references INTEROP-9417 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 task to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Summary

Adds a smoke-scoped variant of acm-tests-clc-create that targets single-cluster creation only, reducing CI runtime from ~8h to ~1.5h.

Changes:

  • New step acm-tests-clc-smoke under ci-operator/step-registry/acm/tests/clc-smoke/
  • OPP configs (ocp4.22, ocp5.0) updated to use the new step
  • acm-tests-clc-destroy post step unchanged

Key differences from acm-tests-clc-create:

Property Full (old) Smoke (new)
Timeout 28800s (8h) 7200s (2h)
CUSTOMER_TAGS (empty) @smoke
Failure handling || : (always passes) Propagates (downstream steps depend on cluster)
CLOUD_PROVIDERS From secret only Overridable via CLOUD_PROVIDERS_OVERRIDE

Context

For OPP interop, we only need CLC to create one managed cluster so downstream steps (acm-fetch-managed-clusters, acm-opp-app) can run. The full lifecycle suite is already validated by ACM's own CI.

Open Items

  • Confirm CUSTOMER_TAGS=@smoke is the correct filter with ACM CLC team (David Huynh, Almen Ng)
  • Validate in pj-rehearse that the smoke scope still creates at least 1 managed cluster
  • Confirm CLOUD_PROVIDERS secret already limits to AWS (or set CLOUD_PROVIDERS_OVERRIDE=aws)

Test Plan

  • Rehearsal passes with new step
  • At least 1 managed cluster created
  • Downstream acm-fetch-managed-clusters and acm-opp-app succeed
  • Step completes in under 2 hours

/cc @dtthuynh @vboulos

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

openshift-ci Bot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 12, 2026
@coderabbitai

coderabbitai Bot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

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

Review profile: CHILL

Plan: Pro Plus

Run ID: 58ebc196-badd-42d4-808a-79fd56d17f5f

📥 Commits

Reviewing files that changed from the base of the PR and between f61fdbc and 674dd8f.

📒 Files selected for processing (2)
  • ci-operator/step-registry/acm/tests/clc-smoke/acm-tests-clc-smoke-ref.metadata.json
  • ci-operator/step-registry/acm/tests/clc-smoke/acm-tests-clc-smoke-ref.yaml
🚧 Files skipped from review as they are similar to previous changes (2)
  • ci-operator/step-registry/acm/tests/clc-smoke/acm-tests-clc-smoke-ref.metadata.json
  • ci-operator/step-registry/acm/tests/clc-smoke/acm-tests-clc-smoke-ref.yaml

Walkthrough

The PR adds the ACM CLC smoke test step, its execution script, ownership metadata, and documentation. It replaces acm-tests-clc-create in the OCP 4.22 and OCP 5.0 AWS interop workflows.

Changes

CLC smoke test integration

Layer / File(s) Summary
Define the CLC smoke test step
ci-operator/step-registry/acm/tests/clc-smoke/acm-tests-clc-smoke-ref.yaml, ci-operator/step-registry/acm/tests/clc-smoke/acm-tests-clc-smoke-ref.metadata.json, ci-operator/step-registry/acm/tests/clc-smoke/OWNERS, ci-operator/step-registry/acm/tests/clc-smoke/README.md
Adds the step definition, metadata, ownership assignments, timeout, resources, credential mounts, environment variables, and documented behavior.
Implement smoke test execution
ci-operator/step-registry/acm/tests/clc-smoke/acm-tests-clc-smoke-commands.sh
Prepares credentials, configures Cypress and cloud settings, runs CLC interop commands, clears secrets, collects reports, and returns the interop status.
Replace the AWS interop test step
ci-operator/config/stolostron/policy-collection/stolostron-policy-collection-main__ocp4.22.yaml, ci-operator/config/stolostron/policy-collection/stolostron-policy-collection-main__ocp5.0.yaml
Changes both AWS interop workflows to run acm-tests-clc-smoke instead of acm-tests-clc-create.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Mergeability Score: ⚪ Minimal · up to 674dd

The PR adds a scoped smoke step with a shorter timeout and explicit failure propagation; no actionable merge-blocking risk remains beyond normal checks and review.

Sequence Diagram(s)

sequenceDiagram
  participant AWSInterop
  participant CLCSmokeStep
  participant SmokeCommands
  participant ArtifactStorage
  AWSInterop->>CLCSmokeStep: invoke acm-tests-clc-smoke
  CLCSmokeStep->>SmokeCommands: run configured command
  SmokeCommands->>SmokeCommands: prepare credentials and test environment
  SmokeCommands->>SmokeCommands: run CLC interop commands
  SmokeCommands->>ArtifactStorage: copy reports
  SmokeCommands-->>CLCSmokeStep: return interop status
Loading

Possibly related PRs

  • openshift/release#83360: Replaces the same AWS interop test step in the same policy-collection configuration files with a different test implementation.

Suggested reviewers: dtthuynh, vboulos


Important

Pre-merge checks failed

Please resolve all errors before merging. Addressing warnings is optional.

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
No-Sensitive-Data-In-Logs ❓ Inconclusive The new script disables xtrace while handling AWS credentials and the hub password, runs the child with bash +x, and logs no secret values. No need
✅ Passed checks (14 passed)
Check name Status Explanation
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, shell, metadata, ownership, and documentation; the full diff adds no Ginkgo title calls or dynamic test titles.
Test Structure And Quality ✅ Passed The PR changes only YAML, shell, JSON, Markdown, and OWNERS files; it adds no Ginkgo test code or It/BeforeEach/AfterEach/Eventually calls for this check to assess.
Microshift Test Compatibility ✅ Passed The PR adds CI YAML, shell, documentation, and metadata only; the diff contains no new Ginkgo e2e tests or It/Describe/Context/When constructs to assess for MicroShift compatibility.
Single Node Openshift (Sno) Test Compatibility ✅ Passed The diff adds a CI step, shell script, YAML, metadata, and documentation only; it adds no Ginkgo e2e tests or multi-node assumptions covered by this check.
Topology-Aware Scheduling Compatibility ✅ Passed The diff only adds CI step files and swaps test references; it introduces no deployment/controller code or topology-sensitive scheduling constraints.
Ote Binary Stdout Contract ✅ Passed The full PR diff changes only YAML, metadata, README, OWNERS, and Bash files; it adds no Go code or OTE process-level stdout writes.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed The PR adds a CI shell/registry step and invokes existing Cypress CLC tests; the diff adds no Ginkgo tests or IPv4-specific network code.
No-Weak-Crypto ✅ Passed The PR adds no MD5, SHA1, DES, RC4, Blowfish, ECB, custom crypto, or secret/token comparison; the repository SHA1 use is in an unchanged unrelated step.
Container-Privileges ✅ Passed The complete PR diff adds no privileged, hostPID, hostNetwork, hostIPC, SYS_ADMIN, allowPrivilegeEscalation, or securityContext settings; the new step reuses the existing clc-ui-e2e image.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly identifies the new acm-tests-clc-smoke step and its reduced CLC scope, which matches the main changes.
✨ 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.

@openshift-ci

openshift-ci Bot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: amp-rh
Once this PR has been reviewed and has the lgtm label, please assign dhaiducek for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

The existing acm-tests-clc-create step already creates only 1 AWS
managed cluster (~50 min runtime) but carries a 28800s (8h) timeout
and suppresses failures with || :. This new step provides:

- Right-sized timeout: 5400s (90 min) vs 28800s
- Strict failure propagation: no || : so downstream steps fail fast
  if cluster creation does not succeed

No CUSTOMER_TAGS or CLOUD_PROVIDERS changes needed; the existing
test image already scopes to single-cluster creation via
TEST_STAGE=OCPInterop-create internally.

Update OPP interop configs (ocp4.22, ocp5.0) to use the new step.
The acm-tests-clc-destroy post step remains unchanged.
@amp-rh
amp-rh force-pushed the interop-9417-clc-smoke branch from c08f512 to 4886163 Compare August 12, 2026 21:29

@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.

Actionable comments posted: 2

🤖 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.

Inline comments:
In
`@ci-operator/step-registry/acm/tests/clc-smoke/acm-tests-clc-smoke-commands.sh`:
- Line 2: Update the tracing setup around the test invocation in the shell
script so expanded CYPRESS_BASE_URL and CYPRESS_HUB_API_URL assignments are
never emitted by parent-shell tracing; disable tracing in the current shell
through the commands covering lines 47-51, and add a brief comment documenting
that tracing is disabled to protect cluster endpoints.
- Around line 47-55: Update the invocation of execute_clc_interop_commands.sh to
run within an if block that captures its exit status without terminating the
step immediately. Ensure reports are copied to ARTIFACT_DIR and
CYPRESS_OPTIONS_HUB_PASSWORD is unset before returning the captured failure
status.
🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

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

Review profile: CHILL

Plan: Pro Plus

Run ID: 79985e4f-a7ec-4729-8f6d-ed1b0a7ebe5d

📥 Commits

Reviewing files that changed from the base of the PR and between b185ec1 and 4886163.

📒 Files selected for processing (7)
  • ci-operator/config/stolostron/policy-collection/stolostron-policy-collection-main__ocp4.22.yaml
  • ci-operator/config/stolostron/policy-collection/stolostron-policy-collection-main__ocp5.0.yaml
  • ci-operator/step-registry/acm/tests/clc-smoke/OWNERS
  • ci-operator/step-registry/acm/tests/clc-smoke/README.md
  • ci-operator/step-registry/acm/tests/clc-smoke/acm-tests-clc-smoke-commands.sh
  • ci-operator/step-registry/acm/tests/clc-smoke/acm-tests-clc-smoke-ref.metadata.json
  • ci-operator/step-registry/acm/tests/clc-smoke/acm-tests-clc-smoke-ref.yaml

@amp-rh

amp-rh commented Aug 13, 2026

Copy link
Copy Markdown
Contributor Author

/test all

amp-rh added 2 commits August 13, 2026 11:30
- Keep tracing disabled through cluster endpoint assignments to prevent
  logging CYPRESS_BASE_URL and CYPRESS_HUB_API_URL in CI output
- Capture test exit status so reports are always copied to ARTIFACT_DIR
  before propagating the failure
- Add trailing newline to metadata.json
- Replace silent [ -n ] && [ -n ] with explicit error message on
  credential extraction failure for faster CI triage
- Use jq --rawfile for AWS secret key to keep it off the process
  command line (awsAccKeyID kept as --arg since semi-public)
@amp-rh

amp-rh commented Aug 13, 2026

Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-stolostron-policy-collection-main-ocp4.22-interop-opp-aws

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@amp-rh

amp-rh commented Aug 13, 2026

Copy link
Copy Markdown
Contributor Author

/test all

- Revert trailing newline in metadata.json (auto-generated file must
  match generator output exactly)
- Declare SKIP_OCP_DEPLOY in YAML env section for discoverability
- Regenerate metadata via make registry-metadata
@amp-rh

amp-rh commented Aug 13, 2026

Copy link
Copy Markdown
Contributor Author

/test all

@amp-rh

amp-rh commented Aug 13, 2026

Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-stolostron-policy-collection-main-ocp4.22-interop-opp-aws

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@amp-rh: 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]
@amp-rh: 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-stolostron-policy-collection-main-ocp5.0-interop-opp-aws N/A periodic Ci-operator config changed
periodic-ci-stolostron-policy-collection-main-ocp4.22-interop-opp-aws N/A periodic Ci-operator config changed
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.

@amp-rh
amp-rh marked this pull request as ready for review August 14, 2026 11:53
@openshift-ci openshift-ci Bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 14, 2026
@amp-rh

amp-rh commented Aug 14, 2026

Copy link
Copy Markdown
Contributor Author

/pj-rehearse ack

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@openshift-merge-bot openshift-merge-bot Bot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Aug 14, 2026
@openshift-ci

openshift-ci Bot commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

@amp-rh: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/rehearse/periodic-ci-stolostron-policy-collection-main-ocp4.22-interop-opp-aws 674dd8f link unknown /pj-rehearse periodic-ci-stolostron-policy-collection-main-ocp4.22-interop-opp-aws

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.

@openshift-ci-robot

openshift-ci-robot commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

@amp-rh: This pull request references INTEROP-9417 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 task to target the "5.1.0" version, but no target version was set.

Details

In response to this:

Summary

Adds acm-tests-clc-smoke, a right-sized variant of acm-tests-clc-create for OPP interop jobs.

Problem: acm-tests-clc-create has a 28800s (8h) timeout and suppresses all failures with || :, even though it only creates 1 AWS managed cluster in ~50 minutes. When CLC fails silently, downstream steps (acm-fetch-managed-clusters, acm-opp-app) run against a missing cluster and produce confusing failures.

Solution: New step with behavioral differences:

Property acm-tests-clc-create acm-tests-clc-smoke
Timeout 28800s (8h) 5400s (90 min)
Failure handling || : (always passes) Propagates errors (exit code captured, reports always collected)
Xtrace discipline Leaks cluster endpoints Tracing disabled through all sensitive assignments
Credential validation Silent exit on missing creds Explicit error message on extraction failure
Secret handling AWS key in process args jq --rawfile keeps secret off cmdline

Reviewer Guide

Start here: acm-tests-clc-smoke-ref.yaml shows the step definition (timeout, credentials, env vars).

Core behavioral changes in acm-tests-clc-smoke-commands.sh vs acm-tests-clc-create:

  1. Failure propagation with report preservation: Exit code captured via || clcStatus=$? so reports are always copied to ARTIFACT_DIR before propagating the failure.
  2. Xtrace discipline: Tracing stays disabled (set +x) from password extraction through test execution, preventing cluster endpoint URLs from appearing in CI logs.
  3. Credential validation: Explicit error message (echo "ERROR: ..." 1>&2; exit 1) instead of silent [ -n ] && [ -n ] that exits with no diagnostic.
  4. Secret handling: AWS secret key passed via jq --rawfile to keep it off the process argument list.

Config changes (2 files, 1-line each): swap acm-tests-clc-createacm-tests-clc-smoke in the test section. The acm-tests-clc-destroy post step is unchanged.

Risk: If CLC has transient failures that the || : was masking, this step will now fail the job. That's intentional (fail fast so we triage the real issue instead of debugging missing-cluster errors in downstream steps). The 90-min timeout provides ~80% headroom over the observed ~50 min average.

Changes

  • New step acm-tests-clc-smoke under ci-operator/step-registry/acm/tests/clc-smoke/
  • OPP configs (ocp4.22, ocp5.0) updated to use the new step
  • acm-tests-clc-destroy post step unchanged

Test Plan

  • Rehearsal passes with new step
  • Downstream acm-fetch-managed-clusters and acm-opp-app succeed
  • Step completes in under 90 minutes
  • CLC failure correctly propagates (no silent pass-through)

/cc @dtthuynh @vboulos

Rehearsal validation

Steps in this PR: acm-tests-clc-smoke (new step)

This step is not included in the batch PR (#83405). It was rehearsed independently via opp-aws-4.22. The rehearsal failed at an infrastructure level unrelated to this step. Structural CI checks pass, and the step script follows established patterns from the existing acm-tests-clc-create step.

Rehearsal ack rationale: All rehearsal failures are caused by known infrastructure issues (ACS upstream scanner timeout, ACM S3 credential rotation) unrelated to this PR's changes. All structural CI checks (ci-operator-config, ci-operator-registry, step-registry-shellcheck, yamllint, generated-config) pass. See batch PR #83405 for full rehearsal results and analysis.

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.

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

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants