OCPBUGS-84114: Fix base domain to match Route53 credentials - #80531
Conversation
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>
WalkthroughThe ChangesHyperShift OpenStack E2E Base Domain Update
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 15✅ Passed checks (15 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
[REHEARSALNOTIFIER]
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 Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
@stephenfin: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
/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. |
|
@stephenfin: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
@stephenfin: This pull request references Jira Issue OCPBUGS-84114, which is valid. 3 validation(s) were run on this bug
The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
[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 DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@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. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
…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>
…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>
|
Fix included in release 5.0.0-0.nightly-2026-06-26-082905 |
…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>
…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>
…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>
…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>
…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>
…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>
…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>
PR #80321 (4b47d13) switched the OpenStack e2e execute step from the generic
.awscredtohypershift-pool-aws-credentials, which owns theci.hypershift.devcluster.openshift.comRoute53 zone. However, the--e2e.base-domainflag was left asorigin-ci-int-aws.dev.rhcloud.com, which is owned by theshiftstack-awscredential. This mismatch causesLookupZoneto fail becausehypershift-pool-aws-credentialscannot findorigin-ci-int-aws.dev.rhcloud.comamong 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.shwas modified to change the--e2e.base-domainflag fromorigin-ci-int-aws.dev.rhcloud.comtoci.hypershift.devcluster.openshift.com.Why this matters:
A previous change updated the OpenStack e2e test to use
hypershift-pool-aws-credentialsinstead of generic AWS credentials. However, the base domain flag was not updated accordingly. Sincehypershift-pool-aws-credentialsowns the Route53 hosted zoneci.hypershift.devcluster.openshift.com(notorigin-ci-int-aws.dev.rhcloud.com), the mismatch was causing Route53LookupZoneoperations 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.