Skip to content

OCPBUGS-84114: Fix base domain to match Route53 credentials - #80531

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
shiftstack:fix-hypershift-gate
Jun 15, 2026
Merged

OCPBUGS-84114: Fix base domain to match Route53 credentials#80531
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
shiftstack:fix-hypershift-gate

Conversation

@stephenfin

@stephenfin stephenfin commented Jun 15, 2026

Copy link
Copy Markdown
Contributor

PR #80321 (4b47d13) switched the OpenStack e2e execute step from the generic .awscred to hypershift-pool-aws-credentials, which owns the ci.hypershift.devcluster.openshift.com Route53 zone. However, the --e2e.base-domain flag was left as origin-ci-int-aws.dev.rhcloud.com, which is owned by the shiftstack-aws credential. This mismatch causes LookupZone to fail because hypershift-pool-aws-credentials cannot find origin-ci-int-aws.dev.rhcloud.com among its hosted zones.

Align the base domain with the credentials by switching to ci.hypershift.devcluster.openshift.com, matching the pattern used by the AWS nested e2e step (hypershift-aws-run-e2e-nested-commands.sh).

Summary by CodeRabbit

This PR fixes a configuration mismatch in the HyperShift OpenStack e2e test setup. The change updates the base domain for Route53 lookups to align with the AWS credentials being used.

What changed:
The file ci-operator/step-registry/hypershift/openstack/e2e/execute/hypershift-openstack-e2e-execute-commands.sh was modified to change the --e2e.base-domain flag from origin-ci-int-aws.dev.rhcloud.com to ci.hypershift.devcluster.openshift.com.

Why this matters:
A previous change updated the OpenStack e2e test to use hypershift-pool-aws-credentials instead of generic AWS credentials. However, the base domain flag was not updated accordingly. Since hypershift-pool-aws-credentials owns the Route53 hosted zone ci.hypershift.devcluster.openshift.com (not origin-ci-int-aws.dev.rhcloud.com), the mismatch was causing Route53 LookupZone operations to fail with permission errors.

Consistency: This change brings the OpenStack e2e configuration into alignment with the same pattern already used by the AWS nested e2e test configuration.

PR openshift#80321 (4b47d13) switched the OpenStack e2e execute step from the
generic .awscred to hypershift-pool-aws-credentials, which owns the
ci.hypershift.devcluster.openshift.com Route53 zone. However, the
--e2e.base-domain flag was left as origin-ci-int-aws.dev.rhcloud.com,
which is owned by the shiftstack-aws credential. This mismatch causes
LookupZone to fail because hypershift-pool-aws-credentials cannot find
origin-ci-int-aws.dev.rhcloud.com among its hosted zones.

Align the base domain with the credentials by switching to
ci.hypershift.devcluster.openshift.com, matching the pattern used by the
AWS nested e2e step (hypershift-aws-run-e2e-nested-commands.sh).

Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jun 15, 2026

Copy link
Copy Markdown
Contributor

Walkthrough

The --e2e.base-domain argument in the HyperShift OpenStack E2E execute script is updated from origin-ci-int-aws.dev.rhcloud.com to ci.hypershift.devcluster.openshift.com on a single line.

Changes

HyperShift OpenStack E2E Base Domain Update

Layer / File(s) Summary
Update --e2e.base-domain value
ci-operator/step-registry/hypershift/openstack/e2e/execute/hypershift-openstack-e2e-execute-commands.sh
Replaces the base domain argument passed to hack/ci-test-e2e.sh with ci.hypershift.devcluster.openshift.com.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 15
✅ Passed checks (15 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
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 This PR only modifies a bash script configuration file (hypershift-openstack-e2e-execute-commands.sh), updating a base domain parameter. The check for stable/deterministic Ginkgo test names is not...
Test Structure And Quality ✅ Passed The PR modifies only a shell script that configures E2E test execution, not Ginkgo test code. The custom check is inapplicable as there are no Ginkgo test files in this PR.
Microshift Test Compatibility ✅ Passed No new Ginkgo e2e tests are added in this PR. The change is solely a shell script parameter update (base domain configuration), not new test code.
Single Node Openshift (Sno) Test Compatibility ✅ Passed This PR does not add new Ginkgo e2e tests. It modifies a shell script configuration parameter for test execution, not test code. The SNO compatibility check is for new test additions and does not a...
Topology-Aware Scheduling Compatibility ✅ Passed PR modifies only a test infrastructure script (CI operator step registry), not deployment manifests, operator code, or controllers. The change is a configuration parameter update for E2E testing, n...
Ote Binary Stdout Contract ✅ Passed PR modifies only shell scripts for CI configuration (hypershift-openstack-e2e-execute-commands.sh), not Go binaries. OTE Binary Stdout Contract check applies only to Go binaries communicating via J...
Ipv6 And Disconnected Network Test Compatibility ✅ Passed PR modifies only a shell script that invokes tests, not new test code. No Ginkgo test definitions (It, Describe, Context, When) are added. Custom check applicability requires new tests to be added.
No-Weak-Crypto ✅ Passed The PR modifies only a bash script configuration file, changing a domain name parameter from origin-ci-int-aws.dev.rhcloud.com to ci.hypershift.devcluster.openshift.com. No cryptographic code, weak...
Container-Privileges ✅ Passed PR modifies only a shell script for test configuration, not container or K8s manifests; container-privileges check is not applicable.
No-Sensitive-Data-In-Logs ✅ Passed The PR changes a domain name flag value in a shell script from one internal hostname to another. No new logging of sensitive data (passwords, tokens, API keys, PII, or session IDs) is introduced. T...
Title check ✅ Passed The title clearly identifies the specific issue being fixed: updating the base domain to match Route53 credentials, which directly corresponds to the main change in the changeset.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

@openshift-ci
openshift-ci Bot requested review from gryf and mandre June 15, 2026 13:54
@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 15, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@stephenfin: 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-cluster-api-provider-openstack-main-e2e-hypershift openshift/cluster-api-provider-openstack presubmit Registry content changed
pull-ci-openshift-cluster-api-provider-openstack-release-5.1-e2e-hypershift openshift/cluster-api-provider-openstack presubmit Registry content changed
pull-ci-openshift-cluster-api-provider-openstack-release-5.0-e2e-hypershift openshift/cluster-api-provider-openstack presubmit Registry content changed
pull-ci-openshift-cluster-api-provider-openstack-release-4.23-e2e-hypershift openshift/cluster-api-provider-openstack presubmit Registry content changed
pull-ci-openshift-hypershift-main-e2e-openstack-aws openshift/hypershift presubmit Registry content changed
pull-ci-openshift-hypershift-release-5.1-e2e-openstack-aws openshift/hypershift presubmit Registry content changed
pull-ci-openshift-hypershift-release-5.0-e2e-openstack-aws openshift/hypershift presubmit Registry content changed
pull-ci-openshift-hypershift-release-4.23-e2e-openstack-aws openshift/hypershift presubmit Registry content changed
pull-ci-openshift-openstack-resource-controller-main-e2e-hypershift openshift/openstack-resource-controller presubmit Registry content changed
pull-ci-openshift-openstack-resource-controller-release-5.1-e2e-hypershift openshift/openstack-resource-controller presubmit Registry content changed
pull-ci-openshift-openstack-resource-controller-release-5.0-e2e-hypershift openshift/openstack-resource-controller presubmit Registry content changed
pull-ci-openshift-openstack-resource-controller-release-4.23-e2e-hypershift openshift/openstack-resource-controller presubmit Registry content changed
pull-ci-openshift-openstack-resource-controller-release-4.22-e2e-hypershift openshift/openstack-resource-controller presubmit Registry content changed
pull-ci-openshift-openstack-resource-controller-release-4.21-e2e-hypershift openshift/openstack-resource-controller presubmit Registry content changed
pull-ci-openshift-openstack-resource-controller-release-4.20-e2e-hypershift openshift/openstack-resource-controller presubmit Registry content changed
pull-ci-openshift-openstack-resource-controller-release-4.19-e2e-hypershift openshift/openstack-resource-controller presubmit Registry content changed
pull-ci-openshift-machine-config-operator-main-e2e-openstack-hypershift openshift/machine-config-operator presubmit Registry content changed
pull-ci-openshift-machine-config-operator-release-5.1-e2e-openstack-hypershift openshift/machine-config-operator presubmit Registry content changed
pull-ci-openshift-machine-config-operator-release-5.0-e2e-openstack-hypershift openshift/machine-config-operator presubmit Registry content changed
pull-ci-openshift-machine-config-operator-release-4.23-e2e-openstack-hypershift openshift/machine-config-operator presubmit Registry content changed
pull-ci-openshift-machine-config-operator-release-4.22-e2e-openstack-hypershift openshift/machine-config-operator presubmit Registry content changed
pull-ci-openshift-machine-config-operator-release-4.21-e2e-openstack-hypershift openshift/machine-config-operator presubmit Registry content changed
pull-ci-openshift-machine-config-operator-release-4.20-e2e-openstack-hypershift openshift/machine-config-operator presubmit Registry content changed
pull-ci-openshift-machine-config-operator-release-4.19-e2e-openstack-hypershift openshift/machine-config-operator presubmit Registry content changed
pull-ci-openshift-machine-config-operator-release-4.18-e2e-openstack-hypershift openshift/machine-config-operator presubmit Registry content changed

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

@openshift-ci

openshift-ci Bot commented Jun 15, 2026

Copy link
Copy Markdown
Contributor

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

@stephenfin

Copy link
Copy Markdown
Contributor Author

/pj-rehearse ack

The hypershift gate is currently broken. We're fixing it in openshift/hypershift#8687. We can't do dependent checks from this repo so we need to merge this first.

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@stephenfin: 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 Jun 15, 2026
@stephenfin stephenfin changed the title hypershift/openstack: fix base domain to match Route53 credentials OCPBUGS-84114: Fix base domain to match Route53 credentials Jun 15, 2026
@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Jun 15, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@stephenfin: This pull request references Jira Issue OCPBUGS-84114, 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:

PR #80321 (4b47d13) switched the OpenStack e2e execute step from the generic .awscred to hypershift-pool-aws-credentials, which owns the ci.hypershift.devcluster.openshift.com Route53 zone. However, the --e2e.base-domain flag was left as origin-ci-int-aws.dev.rhcloud.com, which is owned by the shiftstack-aws credential. This mismatch causes LookupZone to fail because hypershift-pool-aws-credentials cannot find origin-ci-int-aws.dev.rhcloud.com among its hosted zones.

Align the base domain with the credentials by switching to ci.hypershift.devcluster.openshift.com, matching the pattern used by the AWS nested e2e step (hypershift-aws-run-e2e-nested-commands.sh).

Summary by CodeRabbit

This PR fixes a configuration mismatch in the HyperShift OpenStack e2e test setup. The change updates the base domain for Route53 lookups to align with the AWS credentials being used.

What changed:
The file ci-operator/step-registry/hypershift/openstack/e2e/execute/hypershift-openstack-e2e-execute-commands.sh was modified to change the --e2e.base-domain flag from origin-ci-int-aws.dev.rhcloud.com to ci.hypershift.devcluster.openshift.com.

Why this matters:
A previous change updated the OpenStack e2e test to use hypershift-pool-aws-credentials instead of generic AWS credentials. However, the base domain flag was not updated accordingly. Since hypershift-pool-aws-credentials owns the Route53 hosted zone ci.hypershift.devcluster.openshift.com (not origin-ci-int-aws.dev.rhcloud.com), the mismatch was causing Route53 LookupZone operations to fail with permission errors.

Consistency: This change brings the OpenStack e2e configuration into alignment with the same pattern already used by the AWS nested e2e test configuration.

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.

@mandre mandre left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

/lgtm
/approve

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

openshift-ci Bot commented Jun 15, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mandre, stephenfin

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-merge-bot
openshift-merge-bot Bot merged commit 861b8b0 into openshift:main Jun 15, 2026
10 checks passed
@openshift-merge-bot
openshift-merge-bot Bot deleted the fix-hypershift-gate branch June 15, 2026 14:16
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@stephenfin: Jira Issue OCPBUGS-84114: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-84114 has been moved to the MODIFIED state.

Details

In response to this:

PR #80321 (4b47d13) switched the OpenStack e2e execute step from the generic .awscred to hypershift-pool-aws-credentials, which owns the ci.hypershift.devcluster.openshift.com Route53 zone. However, the --e2e.base-domain flag was left as origin-ci-int-aws.dev.rhcloud.com, which is owned by the shiftstack-aws credential. This mismatch causes LookupZone to fail because hypershift-pool-aws-credentials cannot find origin-ci-int-aws.dev.rhcloud.com among its hosted zones.

Align the base domain with the credentials by switching to ci.hypershift.devcluster.openshift.com, matching the pattern used by the AWS nested e2e step (hypershift-aws-run-e2e-nested-commands.sh).

Summary by CodeRabbit

This PR fixes a configuration mismatch in the HyperShift OpenStack e2e test setup. The change updates the base domain for Route53 lookups to align with the AWS credentials being used.

What changed:
The file ci-operator/step-registry/hypershift/openstack/e2e/execute/hypershift-openstack-e2e-execute-commands.sh was modified to change the --e2e.base-domain flag from origin-ci-int-aws.dev.rhcloud.com to ci.hypershift.devcluster.openshift.com.

Why this matters:
A previous change updated the OpenStack e2e test to use hypershift-pool-aws-credentials instead of generic AWS credentials. However, the base domain flag was not updated accordingly. Since hypershift-pool-aws-credentials owns the Route53 hosted zone ci.hypershift.devcluster.openshift.com (not origin-ci-int-aws.dev.rhcloud.com), the mismatch was causing Route53 LookupZone operations to fail with permission errors.

Consistency: This change brings the OpenStack e2e configuration into alignment with the same pattern already used by the AWS nested e2e test configuration.

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.

kasturinarra pushed a commit to kasturinarra/release that referenced this pull request Jun 15, 2026
…penshift#80531)

PR openshift#80321 (4b47d13) switched the OpenStack e2e execute step from the
generic .awscred to hypershift-pool-aws-credentials, which owns the
ci.hypershift.devcluster.openshift.com Route53 zone. However, the
--e2e.base-domain flag was left as origin-ci-int-aws.dev.rhcloud.com,
which is owned by the shiftstack-aws credential. This mismatch causes
LookupZone to fail because hypershift-pool-aws-credentials cannot find
origin-ci-int-aws.dev.rhcloud.com among its hosted zones.

Align the base domain with the credentials by switching to
ci.hypershift.devcluster.openshift.com, matching the pattern used by the
AWS nested e2e step (hypershift-aws-run-e2e-nested-commands.sh).

Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
kasturinarra pushed a commit to kasturinarra/release that referenced this pull request Jun 19, 2026
…penshift#80531)

PR openshift#80321 (4b47d13) switched the OpenStack e2e execute step from the
generic .awscred to hypershift-pool-aws-credentials, which owns the
ci.hypershift.devcluster.openshift.com Route53 zone. However, the
--e2e.base-domain flag was left as origin-ci-int-aws.dev.rhcloud.com,
which is owned by the shiftstack-aws credential. This mismatch causes
LookupZone to fail because hypershift-pool-aws-credentials cannot find
origin-ci-int-aws.dev.rhcloud.com among its hosted zones.

Align the base domain with the credentials by switching to
ci.hypershift.devcluster.openshift.com, matching the pattern used by the
AWS nested e2e step (hypershift-aws-run-e2e-nested-commands.sh).

Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@openshift-merge-robot

Copy link
Copy Markdown
Contributor

Fix included in release 5.0.0-0.nightly-2026-06-26-082905

krisnababu pushed a commit to krisnababu/release that referenced this pull request Jun 29, 2026
…penshift#80531)

PR openshift#80321 (4b47d13) switched the OpenStack e2e execute step from the
generic .awscred to hypershift-pool-aws-credentials, which owns the
ci.hypershift.devcluster.openshift.com Route53 zone. However, the
--e2e.base-domain flag was left as origin-ci-int-aws.dev.rhcloud.com,
which is owned by the shiftstack-aws credential. This mismatch causes
LookupZone to fail because hypershift-pool-aws-credentials cannot find
origin-ci-int-aws.dev.rhcloud.com among its hosted zones.

Align the base domain with the credentials by switching to
ci.hypershift.devcluster.openshift.com, matching the pattern used by the
AWS nested e2e step (hypershift-aws-run-e2e-nested-commands.sh).

Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
krisnababu pushed a commit to oharan2/release that referenced this pull request Jul 3, 2026
…penshift#80531)

PR openshift#80321 (4b47d13) switched the OpenStack e2e execute step from the
generic .awscred to hypershift-pool-aws-credentials, which owns the
ci.hypershift.devcluster.openshift.com Route53 zone. However, the
--e2e.base-domain flag was left as origin-ci-int-aws.dev.rhcloud.com,
which is owned by the shiftstack-aws credential. This mismatch causes
LookupZone to fail because hypershift-pool-aws-credentials cannot find
origin-ci-int-aws.dev.rhcloud.com among its hosted zones.

Align the base domain with the credentials by switching to
ci.hypershift.devcluster.openshift.com, matching the pattern used by the
AWS nested e2e step (hypershift-aws-run-e2e-nested-commands.sh).

Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
andrej1991 pushed a commit to andrej1991/release that referenced this pull request Jul 6, 2026
…penshift#80531)

PR openshift#80321 (4b47d13) switched the OpenStack e2e execute step from the
generic .awscred to hypershift-pool-aws-credentials, which owns the
ci.hypershift.devcluster.openshift.com Route53 zone. However, the
--e2e.base-domain flag was left as origin-ci-int-aws.dev.rhcloud.com,
which is owned by the shiftstack-aws credential. This mismatch causes
LookupZone to fail because hypershift-pool-aws-credentials cannot find
origin-ci-int-aws.dev.rhcloud.com among its hosted zones.

Align the base domain with the credentials by switching to
ci.hypershift.devcluster.openshift.com, matching the pattern used by the
AWS nested e2e step (hypershift-aws-run-e2e-nested-commands.sh).

Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
TimurMP pushed a commit to TimurMP/release that referenced this pull request Jul 8, 2026
…penshift#80531)

PR openshift#80321 (4b47d13) switched the OpenStack e2e execute step from the
generic .awscred to hypershift-pool-aws-credentials, which owns the
ci.hypershift.devcluster.openshift.com Route53 zone. However, the
--e2e.base-domain flag was left as origin-ci-int-aws.dev.rhcloud.com,
which is owned by the shiftstack-aws credential. This mismatch causes
LookupZone to fail because hypershift-pool-aws-credentials cannot find
origin-ci-int-aws.dev.rhcloud.com among its hosted zones.

Align the base domain with the credentials by switching to
ci.hypershift.devcluster.openshift.com, matching the pattern used by the
AWS nested e2e step (hypershift-aws-run-e2e-nested-commands.sh).

Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
SachinNinganure pushed a commit to SachinNinganure/release that referenced this pull request Jul 20, 2026
…penshift#80531)

PR openshift#80321 (4b47d13) switched the OpenStack e2e execute step from the
generic .awscred to hypershift-pool-aws-credentials, which owns the
ci.hypershift.devcluster.openshift.com Route53 zone. However, the
--e2e.base-domain flag was left as origin-ci-int-aws.dev.rhcloud.com,
which is owned by the shiftstack-aws credential. This mismatch causes
LookupZone to fail because hypershift-pool-aws-credentials cannot find
origin-ci-int-aws.dev.rhcloud.com among its hosted zones.

Align the base domain with the credentials by switching to
ci.hypershift.devcluster.openshift.com, matching the pattern used by the
AWS nested e2e step (hypershift-aws-run-e2e-nested-commands.sh).

Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
amogh-redhat pushed a commit to amogh-redhat/release that referenced this pull request Aug 5, 2026
…penshift#80531)

PR openshift#80321 (4b47d13) switched the OpenStack e2e execute step from the
generic .awscred to hypershift-pool-aws-credentials, which owns the
ci.hypershift.devcluster.openshift.com Route53 zone. However, the
--e2e.base-domain flag was left as origin-ci-int-aws.dev.rhcloud.com,
which is owned by the shiftstack-aws credential. This mismatch causes
LookupZone to fail because hypershift-pool-aws-credentials cannot find
origin-ci-int-aws.dev.rhcloud.com among its hosted zones.

Align the base domain with the credentials by switching to
ci.hypershift.devcluster.openshift.com, matching the pattern used by the
AWS nested e2e step (hypershift-aws-run-e2e-nested-commands.sh).

Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
TimurMP pushed a commit to TimurMP/release that referenced this pull request Sep 5, 2026
…penshift#80531)

PR openshift#80321 (4b47d13) switched the OpenStack e2e execute step from the
generic .awscred to hypershift-pool-aws-credentials, which owns the
ci.hypershift.devcluster.openshift.com Route53 zone. However, the
--e2e.base-domain flag was left as origin-ci-int-aws.dev.rhcloud.com,
which is owned by the shiftstack-aws credential. This mismatch causes
LookupZone to fail because hypershift-pool-aws-credentials cannot find
origin-ci-int-aws.dev.rhcloud.com among its hosted zones.

Align the base domain with the credentials by switching to
ci.hypershift.devcluster.openshift.com, matching the pattern used by the
AWS nested e2e step (hypershift-aws-run-e2e-nested-commands.sh).

Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants