OCPBUGS-98323: fix proxy conformance by adding AWS_REGION_OVERWRITE to blackholenetwork step by jparrill · Pull Request #81729 · openshift/release

jparrill · 2026-07-10T09:26:07Z

Summary

Add AWS_REGION_OVERWRITE support to the ipi-conf-aws-blackholenetwork step, matching the existing pattern in ipi-conf-aws
Set AWS_REGION_OVERWRITE: us-east-1 in the HyperShift e2e-aws-ovn-proxy-conformance periodics for 4.23 and 5.0

Fixes: https://issues.redhat.com/browse/OCPBUGS-98323

Root Cause

The e2e-aws-ovn-proxy-conformance periodic has been at 0% pass rate since the cluster profile was changed from hypershift to hypershift-aws (26615a37031, Jan 2026). The hypershift-aws Boskos leases are UUID-based quota slices, so LEASED_RESOURCE is a UUID (e.g. 2e146b47-6dfa-426a-a6bf-28756a23a1c3) instead of an AWS region name.

Two steps in the proxy chain used LEASED_RESOURCE as the AWS region:

ipi-conf-aws-blackholenetwork: REGION="${LEASED_RESOURCE}" — CloudFormation calls fail with cloudformation.<uuid>.amazonaws.com
ipi-conf-aws: REGION="${AWS_REGION_OVERWRITE:-${LEASED_RESOURCE}}" — already supports override, just needs it set

Changes

File	Change
`blackholenetwork-commands.sh`	`REGION="${LEASED_RESOURCE}"` → `REGION="${AWS_REGION_OVERWRITE:-${LEASED_RESOURCE}}"`
`blackholenetwork-ref.yaml`	New `AWS_REGION_OVERWRITE` env (default empty → falls back to `LEASED_RESOURCE`)
4.23 periodics	`AWS_REGION_OVERWRITE: us-east-1` for proxy conformance
5.0 periodics	`AWS_REGION_OVERWRITE: us-east-1` for proxy conformance

Impact on other jobs

The blackholenetwork step is used by 4 workflows. All non-HyperShift consumers use cluster profiles with region-based Boskos leases (openshift-org-aws, aws-mco-qe), so AWS_REGION_OVERWRITE stays empty and falls back to LEASED_RESOURCE (a real region). No behavior change for them.

Test plan

make jobs passes locally
Rehearse: ipi-conf-aws-blackholenetwork step passes with us-east-1 (confirmed in first rehearse run)
Full rehearse: /pj-rehearse periodic-ci-openshift-hypershift-release-4.23-periodics-e2e-aws-ovn-proxy-conformance

/cc @wking @sjenning

🤖 Generated with Claude Code

Summary by CodeRabbit

Adds AWS_REGION_OVERWRITE support to AWS blackholenetwork setup and teardown steps, falling back to LEASED_RESOURCE when unset.
Configures HyperShift AWS proxy conformance periodics for 4.23 and 5.0 to use us-east-1, avoiding UUID lease values being interpreted as AWS regions.
Rehearsal confirmed the updated steps succeeded; installation later encountered AWS API connectivity issues in the proxy VPC.

openshift-ci-robot · 2026-07-10T09:26:14Z

@jparrill: This pull request references Jira Issue OCPBUGS-98323, which is invalid:

expected the bug to target the "5.0.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Summary

Add a REGION env override to the ipi-conf-aws-blackholenetwork step, falling back to LEASED_RESOURCE when unset (backwards compatible)

Set REGION: us-east-1 in the HyperShift e2e-aws-ovn-proxy-conformance periodics for 4.23 and 5.0

Fixes: https://issues.redhat.com/browse/OCPBUGS-98323

Root Cause

The e2e-aws-ovn-proxy-conformance periodic has been at 0% pass rate since the cluster profile was changed from hypershift to hypershift-aws (26615a37031, Jan 2026). The hypershift-aws Boskos leases are UUID-based quota slices, so LEASED_RESOURCE is a UUID (e.g. 2e146b47-6dfa-426a-a6bf-28756a23a1c3) instead of an AWS region name. The blackholenetwork step used LEASED_RESOURCE directly as the --region for CloudFormation API calls, producing bogus endpoints like cloudformation.<uuid>.amazonaws.com.

Changes

File Change

blackholenetwork-commands.sh REGION="${LEASED_RESOURCE}" → REGION="${REGION:-${LEASED_RESOURCE}}"

blackholenetwork-ref.yaml New REGION env (default empty → falls back to LEASED_RESOURCE)

4.23 periodics REGION: us-east-1 for proxy conformance

5.0 periodics REGION: us-east-1 for proxy conformance

Test plan

Verify make jobs passes (done locally)

Existing jobs using blackholenetwork with region-based profiles are unaffected (empty REGION falls back to LEASED_RESOURCE)

HyperShift proxy conformance periodic should reach CloudFormation with us-east-1 instead of a UUID

/cc @wking @sjenning

🤖 Generated with Claude Code

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.

coderabbitai · 2026-07-10T09:26:54Z

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: Enterprise

Run ID: be914ce8-c539-4972-8c36-a125975f0546

📥 Commits

Reviewing files that changed from the base of the PR and between c9855e8 and cd995fc.

📒 Files selected for processing (6)

ci-operator/config/openshift/hypershift/openshift-hypershift-release-4.23__periodics.yaml
ci-operator/config/openshift/hypershift/openshift-hypershift-release-5.0__periodics.yaml
ci-operator/step-registry/ipi/conf/aws/blackholenetwork/ipi-conf-aws-blackholenetwork-commands.sh
ci-operator/step-registry/ipi/conf/aws/blackholenetwork/ipi-conf-aws-blackholenetwork-ref.yaml
ci-operator/step-registry/ipi/deprovision/aws/blackholenetwork/ipi-deprovision-aws-blackholenetwork-commands.sh
ci-operator/step-registry/ipi/deprovision/aws/blackholenetwork/ipi-deprovision-aws-blackholenetwork-ref.yaml

✅ Files skipped from review due to trivial changes (2)

ci-operator/step-registry/ipi/conf/aws/blackholenetwork/ipi-conf-aws-blackholenetwork-ref.yaml
ci-operator/config/openshift/hypershift/openshift-hypershift-release-5.0__periodics.yaml

🚧 Files skipped from review as they are similar to previous changes (2)

ci-operator/config/openshift/hypershift/openshift-hypershift-release-4.23__periodics.yaml
ci-operator/step-registry/ipi/conf/aws/blackholenetwork/ipi-conf-aws-blackholenetwork-commands.sh

Walkthrough

The blackholenetwork AWS steps now support an explicit region override, and the Hypershift 4.23 and 5.0 proxy conformance jobs set it to us-east-1.

Changes

AWS region override

Layer / File(s)	Summary
Blackholenetwork region resolution `ci-operator/step-registry/ipi/conf/aws/blackholenetwork/`, `ci-operator/step-registry/ipi/deprovision/aws/blackholenetwork/`	Configure and deprovision steps document `AWS_REGION_OVERWRITE` and prefer it over `LEASED_RESOURCE` when selecting the AWS region.
Hypershift periodic job wiring `ci-operator/config/openshift/hypershift/openshift-hypershift-release-{4.23,5.0}__periodics.yaml`	The `e2e-aws-ovn-proxy-conformance` jobs set `AWS_REGION_OVERWRITE` to `us-east-1`.

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

Suggested labels: rehearsals-ack

Suggested reviewers: jhixson74

🚥 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 matches the main change: adding AWS_REGION_OVERWRITE support to the blackholenetwork step for proxy conformance.
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	No Ginkgo titles were added or changed; the PR only updates CI YAML and shell scripts for region override support.
Test Structure And Quality	✅ Passed	PR changes only YAML and shell scripts; no Ginkgo/Gomega test files or specs were touched, so the test-structure check is not applicable.
Microshift Test Compatibility	✅ Passed	No Ginkgo/e2e test files or test additions were changed; the PR only updates CI YAML and shell step scripts.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	No new Ginkgo/e2e tests were added; the PR only changes CI configs and shell step scripts, with no SNO-sensitive test logic.
Topology-Aware Scheduling Compatibility	✅ Passed	Only CI periodics and AWS region-override scripts changed; no pod scheduling, topology, nodeSelector, affinity, or replica logic was introduced.
Ote Binary Stdout Contract	✅ Passed	PASS: PR only changes ci-operator YAML and shell step scripts; no OTE binary main/init/TestMain/Suite code or stdout writes were added.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PR only changes CI configs and shell step env/region logic; no new Ginkgo tests or IPv4/public-network assumptions were added.
No-Weak-Crypto	✅ Passed	Touched files only add AWS region overrides; no MD5/SHA1/DES/RC4/3DES/Blowfish/ECB or secret comparisons found.
Container-Privileges	✅ Passed	No changed manifest or step config adds privileged settings; diff only adds AWS_REGION_OVERWRITE env and region fallback logic.
No-Sensitive-Data-In-Logs	✅ Passed	No new secret/PII-bearing logging was added; existing echoes are status text and a region string only.

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

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

jparrill · 2026-07-10T09:28:25Z

/pj-rehearse periodic-ci-openshift-hypershift-release-4.23-periodics-e2e-aws-ovn-proxy-conformance

openshift-merge-bot · 2026-07-10T09:28:28Z

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

jparrill · 2026-07-10T09:53:33Z

/pj-rehearse periodic-ci-openshift-hypershift-release-4.23-periodics-e2e-aws-ovn-proxy-conformance

openshift-merge-bot · 2026-07-10T09:58:35Z

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

jparrill · 2026-07-10T10:00:29Z

/pj-rehearse periodic-ci-openshift-hypershift-release-4.23-periodics-e2e-aws-ovn-proxy-conformance

jparrill · 2026-07-10T10:02:10Z

/jira refresh

openshift-ci-robot · 2026-07-10T10:02:16Z

@jparrill: This pull request references Jira Issue OCPBUGS-98323, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (5.0.0) matches configured target version for branch (5.0.0)
bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Details

In response to this:

/jira refresh

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-merge-bot · 2026-07-10T10:05:32Z

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

jparrill · 2026-07-10T10:08:40Z

/pj-rehearse periodic-ci-openshift-hypershift-release-4.23-periodics-e2e-aws-ovn-proxy-conformance

openshift-merge-bot · 2026-07-10T10:08:43Z

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

YamunadeviShanmugam · 2026-07-10T10:56:41Z

/pj-rehearse periodic-ci-openshift-hypershift-release-4.23-periodics-e2e-aws-ovn-proxy-conformance

openshift-merge-bot · 2026-07-10T10:59:40Z

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

YamunadeviShanmugam · 2026-07-10T11:29:40Z

This is a clean up comment that is failing in this job
-> When cluster profile changed from hypershift to hypershift-aws, LEASED_RESOURCE became a UUID instead of an AWS region name
-> This PR correctly fixes ipi-conf-aws-blackholenetwork by adding AWS_REGION_OVERWRITE support (line 16 in the commands.sh changed from REGION="${LEASED_RESOURCE}" to REGION="${AWS_REGION_OVERWRITE:-${LEASED_RESOURCE}}")
-> Install fails : The installer fails to create EC2 client during manifest creation
-> The teardown step ipi-deprovision-aws-blackholenetwork still uses REGION="${LEASED_RESOURCE}" on line 16, so it tries to call cloudformation.300c1373-396f-4dd0-90f4-67d354d8f9d1.amazonaws.com and fails
-> HyperShift destroy fails: Because the cluster never fully created (install failed), there's no HostedCluster object and no infrastructure ID, so hypershift destroy can't clean up

@jparrill : Could you please fix the deprovisioning step as well

in ci-operator/step-registry/ipi/deprovision/aws/blackholenetwork/ipi-deprovision-aws-blackholenetwork-commands.sh

Suggested changes:
REGION="${LEASED_RESOURCE}"

To:
REGION="${AWS_REGION_OVERWRITE:-${LEASED_RESOURCE}}"

and adding the env var to ipi-deprovision-aws-blackholenetwork-ref.yaml.

jparrill · 2026-07-10T12:43:25Z

Rehearse analysis

The rehearse job failed, but not in any step our PR touches. Breakdown:

Step	Result	Notes
`ipi-conf-aws-blackholenetwork`	✅ SUCCESS	Previously crashed with `cloudformation.<uuid>.amazonaws.com` — now uses `us-east-1` correctly
`ipi-conf-aws`	✅ SUCCESS	`AWS_REGION_OVERWRITE=us-east-1` applied
`ipi-conf-aws-proxy`	✅ SUCCESS	Reads region from install-config, now gets `us-east-1`
`ipi-install-install`	❌ FAILURE	OpenShift installer fails with EOF errors creating EC2 client — cannot reach AWS EC2 API from inside the proxy VPC

The ipi-install-install failure is a pre-existing infrastructure issue: the proxy VPC environment has broken connectivity to AWS API endpoints (EC2 in this case, CloudFormation before our fix). This is the same class of issue described in the Jira — the proxy test infrastructure has degraded VPC endpoint connectivity.

This PR is the first of the fixes needed to restore proxy conformance

This PR — fixes the UUID-as-region problem so the job can actually provision the blackhole VPC and configure the install. Without this, the job crashes in ~8 seconds before anything meaningful runs.
Next — the VPC endpoint / network connectivity issues in the proxy test environment need to be investigated and fixed by whoever manages the hypershift-aws AWS account infrastructure.

The rehearse confirms our code change works as intended. The downstream failure is an infrastructure problem that existed before this PR and cannot be fixed from the release repo.

…ckholenetwork step The e2e-aws-ovn-proxy-conformance periodic (4.23/5.0) has been at 0% pass rate since the cluster_profile was changed from 'hypershift' to 'hypershift-aws' (26615a3). The hypershift-aws Boskos leases are UUID-based quota slices, so LEASED_RESOURCE is a UUID instead of an AWS region. The blackholenetwork step used LEASED_RESOURCE directly as the region for CloudFormation calls, producing bogus endpoints like cloudformation.<uuid>.amazonaws.com. Add a REGION env override to the blackholenetwork step (defaulting to empty, which falls back to LEASED_RESOURCE for backwards compat) and set REGION=us-east-1 in the HyperShift proxy conformance periodics. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Juan Manuel Parrilla Madrid <jparrill@redhat.com>

jparrill · 2026-07-10T13:55:29Z

Hey @YamunadeviShanmugam addressed.

openshift-ci-robot · 2026-07-10T13:57:51Z

@jparrill: This pull request references Jira Issue OCPBUGS-98323, which is valid.

3 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (5.0.0) matches configured target version for branch (5.0.0)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Summary

Add AWS_REGION_OVERWRITE support to the ipi-conf-aws-blackholenetwork step, matching the existing pattern in ipi-conf-aws

Set AWS_REGION_OVERWRITE: us-east-1 in the HyperShift e2e-aws-ovn-proxy-conformance periodics for 4.23 and 5.0

Fixes: https://issues.redhat.com/browse/OCPBUGS-98323

Root Cause

The e2e-aws-ovn-proxy-conformance periodic has been at 0% pass rate since the cluster profile was changed from hypershift to hypershift-aws (26615a37031, Jan 2026). The hypershift-aws Boskos leases are UUID-based quota slices, so LEASED_RESOURCE is a UUID (e.g. 2e146b47-6dfa-426a-a6bf-28756a23a1c3) instead of an AWS region name.

Two steps in the proxy chain used LEASED_RESOURCE as the AWS region:

ipi-conf-aws-blackholenetwork: REGION="${LEASED_RESOURCE}" — CloudFormation calls fail with cloudformation.<uuid>.amazonaws.com

ipi-conf-aws: REGION="${AWS_REGION_OVERWRITE:-${LEASED_RESOURCE}}" — already supports override, just needs it set

Changes

File Change

blackholenetwork-commands.sh REGION="${LEASED_RESOURCE}" → REGION="${AWS_REGION_OVERWRITE:-${LEASED_RESOURCE}}"

blackholenetwork-ref.yaml New AWS_REGION_OVERWRITE env (default empty → falls back to LEASED_RESOURCE)

4.23 periodics AWS_REGION_OVERWRITE: us-east-1 for proxy conformance

5.0 periodics AWS_REGION_OVERWRITE: us-east-1 for proxy conformance

Impact on other jobs

The blackholenetwork step is used by 4 workflows. All non-HyperShift consumers use cluster profiles with region-based Boskos leases (openshift-org-aws, aws-mco-qe), so AWS_REGION_OVERWRITE stays empty and falls back to LEASED_RESOURCE (a real region). No behavior change for them.

Test plan

make jobs passes locally

Rehearse: ipi-conf-aws-blackholenetwork step passes with us-east-1 (confirmed in first rehearse run)

Full rehearse: /pj-rehearse periodic-ci-openshift-hypershift-release-4.23-periodics-e2e-aws-ovn-proxy-conformance

/cc @wking @sjenning

🤖 Generated with Claude Code

Summary by CodeRabbit

Adds AWS_REGION_OVERWRITE support to AWS blackholenetwork setup and teardown steps, falling back to LEASED_RESOURCE when unset.

Configures HyperShift AWS proxy conformance periodics for 4.23 and 5.0 to use us-east-1, avoiding UUID lease values being interpreted as AWS regions.

Rehearsal confirmed the updated steps succeeded; installation later encountered AWS API connectivity issues in the proxy VPC.

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-merge-bot · 2026-07-10T13:58:18Z

[REHEARSALNOTIFIER]
@jparrill: 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
pull-ci-openshift-installer-main-e2e-aws-ovn-proxy	openshift/installer	presubmit	Registry content changed
pull-ci-openshift-installer-release-5.1-e2e-aws-ovn-proxy	openshift/installer	presubmit	Registry content changed
pull-ci-openshift-installer-release-5.0-e2e-aws-ovn-proxy	openshift/installer	presubmit	Registry content changed
pull-ci-openshift-installer-release-4.23-e2e-aws-ovn-proxy	openshift/installer	presubmit	Registry content changed
pull-ci-openshift-installer-release-4.22-e2e-aws-ovn-proxy	openshift/installer	presubmit	Registry content changed
pull-ci-openshift-installer-release-4.21-e2e-aws-ovn-proxy	openshift/installer	presubmit	Registry content changed
pull-ci-openshift-installer-release-4.20-e2e-aws-ovn-proxy	openshift/installer	presubmit	Registry content changed
pull-ci-openshift-installer-release-4.19-e2e-aws-ovn-proxy	openshift/installer	presubmit	Registry content changed
pull-ci-openshift-installer-release-4.18-e2e-aws-ovn-proxy	openshift/installer	presubmit	Registry content changed
pull-ci-openshift-installer-release-4.18-altinfra-e2e-aws-ovn-proxy	openshift/installer	presubmit	Registry content changed
pull-ci-openshift-installer-release-4.17-altinfra-e2e-aws-ovn-proxy	openshift/installer	presubmit	Registry content changed
pull-ci-openshift-installer-release-4.17-e2e-aws-ovn-proxy	openshift/installer	presubmit	Registry content changed
pull-ci-openshift-installer-release-4.16-altinfra-e2e-aws-ovn-proxy	openshift/installer	presubmit	Registry content changed
pull-ci-openshift-installer-release-4.16-e2e-aws-ovn-proxy	openshift/installer	presubmit	Registry content changed
pull-ci-openshift-installer-release-4.15-altinfra-e2e-aws-ovn-proxy	openshift/installer	presubmit	Registry content changed
pull-ci-openshift-installer-release-4.15-e2e-aws-ovn-proxy	openshift/installer	presubmit	Registry content changed
pull-ci-openshift-installer-release-4.14-e2e-aws-ovn-proxy	openshift/installer	presubmit	Registry content changed
pull-ci-openshift-installer-release-4.13-e2e-aws-ovn-proxy	openshift/installer	presubmit	Registry content changed
pull-ci-openshift-installer-release-4.12-e2e-aws-ovn-proxy	openshift/installer	presubmit	Registry content changed
pull-ci-openshift-installer-release-4.11-e2e-aws-proxy	openshift/installer	presubmit	Registry content changed
pull-ci-openshift-installer-release-4.10-e2e-aws-proxy	openshift/installer	presubmit	Registry content changed
pull-ci-openshift-installer-release-4.9-e2e-aws-proxy	openshift/installer	presubmit	Registry content changed
pull-ci-openshift-installer-release-4.8-e2e-aws-proxy	openshift/installer	presubmit	Registry content changed
pull-ci-openshift-installer-release-4.7-e2e-aws-proxy	openshift/installer	presubmit	Registry content changed
pull-ci-openshift-installer-release-4.6-e2e-aws-proxy	openshift/installer	presubmit	Registry content changed

A total of 265 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-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.

YamunadeviShanmugam · 2026-07-10T13:59:57Z

Installation is failing due to infra issues, all the changes has been addressed
/lgtm

openshift-ci · 2026-07-10T14:00:46Z

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jparrill, YamunadeviShanmugam
Once this PR has been reviewed and has the lgtm label, please assign patrickdillon 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

openshift-ci · 2026-07-10T14:01:38Z

@jparrill: 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-openshift-hypershift-release-4.23-periodics-e2e-aws-ovn-proxy-conformance	`c9855e8`	link	unknown	`/pj-rehearse periodic-ci-openshift-hypershift-release-4.23-periodics-e2e-aws-ovn-proxy-conformance`

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.

jparrill · 2026-07-10T14:09:14Z

/uncc @sjenning

openshift-ci Bot requested review from sjenning and wking July 10, 2026 09:26

openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jul 10, 2026

jparrill force-pushed the OCPBUGS-98322 branch 2 times, most recently from 2c4f553 to c9855e8 Compare July 10, 2026 09:53

openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jul 10, 2026

jparrill changed the title ~~OCPBUGS-98323: fix proxy conformance by adding REGION override to blackholenetwork step~~ OCPBUGS-98323: fix proxy conformance by adding AWS_REGION_OVERWRITE to blackholenetwork step Jul 10, 2026

openshift-ci Bot assigned YamunadeviShanmugam Jul 10, 2026

openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 10, 2026

openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label Jul 10, 2026

jparrill force-pushed the OCPBUGS-98322 branch from c9855e8 to cd995fc Compare July 10, 2026 13:54

openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 10, 2026

openshift-ci Bot removed the request for review from sjenning July 10, 2026 14:09

Uh oh!

Conversation

jparrill commented Jul 10, 2026 • edited by coderabbitai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Root Cause

Changes

Impact on other jobs

Test plan

Summary by CodeRabbit

Uh oh!

openshift-ci-robot commented Jul 10, 2026

Summary

Root Cause

Changes

Test plan

Uh oh!

coderabbitai Bot commented Jul 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Uh oh!

jparrill commented Jul 10, 2026

Uh oh!

openshift-merge-bot Bot commented Jul 10, 2026

Uh oh!

jparrill commented Jul 10, 2026

Uh oh!

openshift-merge-bot Bot commented Jul 10, 2026

Uh oh!

jparrill commented Jul 10, 2026

Uh oh!

jparrill commented Jul 10, 2026

Uh oh!

openshift-ci-robot commented Jul 10, 2026

Uh oh!

openshift-merge-bot Bot commented Jul 10, 2026

Uh oh!

jparrill commented Jul 10, 2026

Uh oh!

openshift-merge-bot Bot commented Jul 10, 2026

Uh oh!

YamunadeviShanmugam commented Jul 10, 2026

Uh oh!

openshift-merge-bot Bot commented Jul 10, 2026

Uh oh!

YamunadeviShanmugam commented Jul 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

jparrill commented Jul 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Rehearse analysis

This PR is the first of the fixes needed to restore proxy conformance

Uh oh!

jparrill commented Jul 10, 2026

Uh oh!

openshift-ci-robot commented Jul 10, 2026

Summary

Root Cause

Changes

Impact on other jobs

Test plan

Summary by CodeRabbit

Uh oh!

openshift-merge-bot Bot commented Jul 10, 2026

Uh oh!

YamunadeviShanmugam commented Jul 10, 2026

Uh oh!

openshift-ci Bot commented Jul 10, 2026

Uh oh!

openshift-ci Bot commented Jul 10, 2026

Uh oh!

jparrill commented Jul 10, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

jparrill commented Jul 10, 2026 •

edited by coderabbitai Bot

Loading

coderabbitai Bot commented Jul 10, 2026 •

edited

Loading

YamunadeviShanmugam commented Jul 10, 2026 •

edited

Loading

jparrill commented Jul 10, 2026 •

edited

Loading