OCPBUGS-55407: set DNS zone for Azure Stack Hub private clusters by jinyunma · Pull Request #10233 · openshift/installer

jinyunma · 2026-01-19T06:26:55Z

Azure Stack Hub only supports a single DNS zone type (not separate public/private zones). When installing a cluster on Azure Stack Hub, the DNS manifest must specify the PrivateZone field pointing to the base domain zone so that the ingress operator can create *.apps DNS records.

Previously, the DNS manifest generation set PrivateZone only for non-ASH clusters, leaving Azure Stack Hub clusters without zone configuration. This caused the ingress operator to fail with DNS resolution errors.

Azure Stack Hub only supports a single DNS zone type (not separate public/private zones). When installing a cluster on Azure Stack Hub, the DNS manifest must specify the PrivateZone field pointing to the base domain zone so that the ingress operator can create *.apps DNS records. Previously, the DNS manifest generation set PrivateZone only for non-ASH clusters, leaving Azure Stack Hub clusters without zone configuration. This caused the ingress operator to fail with DNS resolution errors. Fixes https://issues.redhat.com/browse/OCPBUGS-55407

openshift-ci-robot · 2026-01-19T06:27:01Z

@jinyunma: This pull request references Jira Issue OCPBUGS-55407, which is invalid:

expected the bug to target the "4.22.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:

Azure Stack Hub only supports a single DNS zone type (not separate public/private zones). When installing a cluster on Azure Stack Hub, the DNS manifest must specify the PrivateZone field pointing to the base domain zone so that the ingress operator can create *.apps DNS records.

Previously, the DNS manifest generation set PrivateZone only for non-ASH clusters, leaving Azure Stack Hub clusters without zone configuration. This caused the ingress operator to fail with DNS resolution errors.

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.

jinyunma · 2026-01-19T11:31:04Z

/jira refresh

openshift-ci-robot · 2026-01-19T11:31:12Z

@jinyunma: This pull request references Jira Issue OCPBUGS-55407, 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 (4.22.0) matches configured target version for branch (4.22.0)
bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @jinyunma

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

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-ci · 2026-01-19T11:31:20Z

@openshift-ci-robot: GitHub didn't allow me to request PR reviews from the following users: jinyunma.

Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs.

Details

In response to this:

@jinyunma: This pull request references Jira Issue OCPBUGS-55407, 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 (4.22.0) matches configured target version for branch (4.22.0)

bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @jinyunma

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

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.

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.

jinyunma · 2026-01-19T11:31:36Z

Tested locally, private cluster installation on azure stack hub succeeded.

$ oc get cm -n kube-system cluster-config-v1 -oyaml
apiVersion: v1
data:
  install-config: |
......
   publish: Internal
    pullSecret: ""
......

$ oc get dns cluster -oyaml
apiVersion: config.openshift.io/v1
kind: DNS
metadata:
  creationTimestamp: "2026-01-19T10:45:42Z"
  generation: 1
  name: cluster
  resourceVersion: "357"
  uid: c1c04a21-7d86-48c8-82e5-25062bfa1b4b
spec:
  baseDomain: jima-ash19b.installer.redhat.wwtatc.com
  platform:
    type: ""
  privateZone:
    id: /subscriptions/de7e09c3-b59a-4c7d-9c77-439c11b92879/resourceGroups/openshiftInstallerRG/providers/Microsoft.Network/dnszones/installer.redhat.wwtatc.com
status: {}

jinyunma · 2026-01-19T11:37:49Z

/test e2e-azurestack

jinyunma · 2026-01-19T14:37:34Z

/test e2e-azurestack

jinyunma · 2026-01-20T08:42:42Z

Installation for job e2e-azurestack in this PR and pre-merge tested job periodic-ci-openshift-openshift-tests-private-release-4.22-amd64-nightly-azure-stack-ipi-private-f28 succeeded.

/cc @patrickdillon @sadasu

sadasu · 2026-01-26T15:38:46Z

/lgtm

The ci/prow/e2e-azurestack job has been perma failing. Are there other errors in there that we need to open bugs for?

jinyunma · 2026-01-27T04:54:39Z

Are there other errors in there that we need to open bugs for?

Most failed cases are related with storage, checked with storage QE, those cases are not supported on Azure Stack Hub, myabe we need to filter to exclude them.

jinyunma · 2026-01-27T04:55:10Z

/verified by jima

openshift-ci-robot · 2026-01-27T04:55:22Z

@jinyunma: This PR has been marked as verified by jima.

Details

In response to this:

/verified by jima

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.

patrickdillon · 2026-02-06T21:08:13Z

/approve

openshift-ci · 2026-02-06T21:09:29Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: patrickdillon

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:

~~OWNERS~~ [patrickdillon]

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-02-06T23:47:36Z

@jinyunma: 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/prow/e2e-azurestack	`5d8a86a`	link	false	`/test e2e-azurestack`

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.

patrickdillon · 2026-02-08T21:50:19Z

/skip
/override ci/prow/artifacts-images

openshift-ci · 2026-02-08T21:50:52Z

@patrickdillon: Overrode contexts on behalf of patrickdillon: ci/prow/artifacts-images

Details

In response to this:

/skip
/override ci/prow/artifacts-images

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.

openshift-ci-robot · 2026-02-09T05:07:46Z

@jinyunma: Jira Issue Verification Checks: Jira Issue OCPBUGS-55407
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-55407 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

Azure Stack Hub only supports a single DNS zone type (not separate public/private zones). When installing a cluster on Azure Stack Hub, the DNS manifest must specify the PrivateZone field pointing to the base domain zone so that the ingress operator can create *.apps DNS records.

Previously, the DNS manifest generation set PrivateZone only for non-ASH clusters, leaving Azure Stack Hub clusters without zone configuration. This caused the ingress operator to fail with DNS resolution errors.

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-robot · 2026-02-17T17:42:36Z

Fix included in accepted release 4.22.0-0.nightly-2026-02-17-112443

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 Jan 19, 2026

openshift-ci Bot requested review from andfasano and rna-afk January 19, 2026 06:27

jinyunma changed the title ~~[WIP] OCPBUGS-55407: set DNS zone for Azure Stack Hub private clusters~~ OCPBUGS-55407: set DNS zone for Azure Stack Hub private clusters Jan 19, 2026

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 Jan 19, 2026

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 Jan 19, 2026

openshift-ci Bot requested review from patrickdillon and sadasu January 20, 2026 08:42

openshift-ci Bot assigned sadasu Jan 26, 2026

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

openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jan 27, 2026

openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 6, 2026

openshift-merge-bot Bot merged commit 69f3d1d into openshift:main Feb 9, 2026
15 checks passed

jinyunma deleted the fix-OCPBUGS-55407 branch February 9, 2026 05:47

jinyunma mentioned this pull request Feb 12, 2026

Add azure-stack-ipi-private CI jobs openshift/release#73710

Merged

Conversation

jinyunma commented Jan 19, 2026

Uh oh!

openshift-ci-robot commented Jan 19, 2026

Uh oh!

jinyunma commented Jan 19, 2026

Uh oh!

openshift-ci-robot commented Jan 19, 2026

Uh oh!

openshift-ci Bot commented Jan 19, 2026

Uh oh!

jinyunma commented Jan 19, 2026

Uh oh!

jinyunma commented Jan 19, 2026

Uh oh!

jinyunma commented Jan 19, 2026

Uh oh!

jinyunma commented Jan 20, 2026

Uh oh!

sadasu commented Jan 26, 2026

Uh oh!

jinyunma commented Jan 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

jinyunma commented Jan 27, 2026

Uh oh!

openshift-ci-robot commented Jan 27, 2026

Uh oh!

patrickdillon commented Feb 6, 2026

Uh oh!

openshift-ci Bot commented Feb 6, 2026

Uh oh!

openshift-ci Bot commented Feb 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

patrickdillon commented Feb 8, 2026

Uh oh!

openshift-ci Bot commented Feb 8, 2026

Uh oh!

Uh oh!

openshift-ci-robot commented Feb 9, 2026

Uh oh!

openshift-merge-robot commented Feb 17, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

jinyunma commented Jan 27, 2026 •

edited

Loading

openshift-ci Bot commented Feb 6, 2026 •

edited

Loading