[release-4.21] OCPBUGS-67305: fix: disk creation failure in AzureStack env

[openshift-cherrypick-robot]

This is an automated cherry-pick of #114

/assign mpatlasov

[openshift-ci-robot]

@openshift-cherrypick-robot: Jira Issue OCPBUGS-67186 has been cloned as Jira Issue OCPBUGS-67305. Will retitle bug to link to clone.
/retitle [release-4.21] OCPBUGS-67305: fix: disk creation failure in AzureStack env

Details

In response to this:

This is an automated cherry-pick of #114

/assign mpatlasov

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-robot]

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-67305, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected dependent Jira Issue OCPBUGS-67186 to target a version in 4.22.0, but it targets "4.21" instead

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:

This is an automated cherry-pick of #114

/assign mpatlasov

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.

[mpatlasov]

/jira refresh

[openshift-ci-robot]

@mpatlasov: This pull request references Jira Issue OCPBUGS-67305, which is invalid:

• expected dependent Jira Issue OCPBUGS-67186 to target a version in 4.22.0, but it targets "4.21" instead

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.

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.

[mpatlasov]

expected dependent Jira Issue OCPBUGS-67186 to target a version in 4.22.0, but it targets "4.21" instead

When trying to update it in JIRA to 4.22.0, got "Version with id '4.22.0' does not exist." from JIRA

[openshift-ci]

@gpei: This PR was included in a payload test run from openshift/installer#10159
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-openshift-tests-private-release-4.21-amd64-nightly-azure-stack-ipi-f28

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/5a43cbf0-d7f4-11f0-998d-1518920a4393-0

[Phaow]

/jira refresh

[openshift-ci-robot]

@Phaow: This pull request references Jira Issue OCPBUGS-67305, which is invalid:

• expected dependent Jira Issue OCPBUGS-67186 to target a version in 4.22.0, but it targets "4.21" instead

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.

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.

[Phaow]

/jira refresh

[openshift-ci-robot]

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

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.21.0) matches configured target version for branch (4.21.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
• release note text is set and does not match the template
• dependent bug Jira Issue OCPBUGS-67186 is in the state ON_QA, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
• dependent Jira Issue OCPBUGS-67186 targets the "4.22.0" version, which is one of the valid target versions: 4.22.0
• bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (wduan@redhat.com), skipping review request.

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.

[Phaow]

/testwith openshift/azure-disk-csi-driver/master/e2e-azurestack-csi openshift/cloud-provider-azure#152

[openshift-ci]

@Phaow, testwith: could not generate prow job. ERROR:

no ref for requested test included in command. The org, repo, and branch containing the requested test need to be targeted by at least one of the included PRs

[Phaow]

/testwith openshift/azure-disk-csi-driver/release-4.21/e2e-azurestack-csi openshift/cloud-provider-azure#152

[Phaow]

/retest-required

[Phaow]

/testwith openshift/azure-disk-csi-driver/release-4.21/e2e-azurestack-csi openshift/cloud-provider-azure#152

[Phaow]

/retest-required

[Phaow]

/testwith openshift/azure-disk-csi-driver/release-4.21/e2e-azurestack-csi openshift/cloud-provider-azure#152

[mpatlasov]

/test e2e-azurestack-csi

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mpatlasov, openshift-cherrypick-robot

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 [mpatlasov]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[Phaow]

/tide refresh

[Phaow]

The tide seems stuck Waiting for status to be reported — Not mergeable. No Tide query for branch release-4.21 found.

[Phaow]

/verified by CI
The failure cases are caused by system issue Unable to connect to the server (ASH vpn is not stable enough).

[openshift-ci-robot]

@Phaow: This PR has been marked as verified by [CI](https://prow.ci.openshift.org/view/gs/test-platform-results/logs/multi-pr-openshift-azure-disk-csi-driver-116-openshift-cloud-provider-azure-152-e2e-azurestack-csi/2000544538753503232).

Details

In response to this:

/verified by CI
The failure cases are caused by system issue Unable to connect to the server (ASH vpn is not stable enough).

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.

[Phaow]

/test all

[openshift-ci]

@openshift-cherrypick-robot: 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-csi	e8b236d	link	false	/test e2e-azurestack-csi

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.

[Phaow]

/hold

[Phaow]

/hold cancel

[damdo]

/tide refresh

[damdo]

openshift/release#72652 merged now

[Phaow]

/label backport-risk-assessed

[openshift-ci]

@Phaow: Can not set label backport-risk-assessed: Must be member in one of these teams: [openshift-patch-managers openshift-release-oversight openshift-staff-engineers openshift-sustaining-engineers]

Details

In response to this:

/label backport-risk-assessed

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.

[damdo]

@sdodson is backporting to 4.21 on freeze even for bugs? TY

[jsafrane]

IMHO the freeze applies only to features. We still need to fix bugs, especially this one that make upgrade to 4.21 working on Azure Stack Hub.

/label backport-risk-assessed label

[jsafrane]

/label backport-risk-assessed

[openshift-ci-robot]

@openshift-cherrypick-robot: Jira Issue Verification Checks: Jira Issue OCPBUGS-67305
✔️ 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-67305 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:

This is an automated cherry-pick of #114

/assign mpatlasov

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.

[sdodson]

@sdodson is backporting to 4.21 on freeze even for bugs? TY

No, always feel free to backport bug fixes especially when associated with a release blocker.

[openshift-merge-robot]

Fix included in accepted release 4.21.0-0.nightly-2025-12-18-020818