Skip to content

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #10151

/assign jinyunma

@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: Jira Issue OCPBUGS-65610 has been cloned as Jira Issue OCPBUGS-69880. Will retitle bug to link to clone.
/retitle [release-4.18] OCPBUGS-69880: Azure UPI ARM template: use storageAccountId

Details

In response to this:

This is an automated cherry-pick of #10151

/assign jinyunma

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 openshift-ci bot changed the title [release-4.18] OCPBUGS-65610: Azure UPI ARM template: use storageAccountId [release-4.18] OCPBUGS-69880: Azure UPI ARM template: use storageAccountId Dec 19, 2025
@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/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Dec 19, 2025
@openshift-ci-robot
Copy link
Contributor

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

  • expected dependent Jira Issue OCPBUGS-65610 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA 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 #10151

/assign jinyunma

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.

@sadasu
Copy link
Contributor

sadasu commented Jan 6, 2026

/jira-refresh

@sadasu
Copy link
Contributor

sadasu commented Jan 6, 2026

/retest

@jinyunma
Copy link
Contributor

jinyunma commented Jan 9, 2026

/jira refresh

@openshift-ci-robot 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 9, 2026
@openshift-ci-robot
Copy link
Contributor

@jinyunma: This pull request references Jira Issue OCPBUGS-69880, 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.18.z) matches configured target version for branch (4.18.z)
  • bug is in the state New, 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-65610 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-65610 targets the "4.19.z" version, which is one of the valid target versions: 4.19.0, 4.19.z
  • bug has dependents

Requesting review from QA contact:
/cc @gpei

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 openshift-ci bot requested a review from gpei January 9, 2026 08:11
@jinyunma
Copy link
Contributor

jinyunma commented Jan 9, 2026

/test e2e-azure-ovn-upi

@jinyunma
Copy link
Contributor

jinyunma commented Jan 9, 2026

/test e2e-azure-ovn-shared-vpc

@jinyunma
Copy link
Contributor

jinyunma commented Jan 9, 2026

UPI installation succeeded in job e2e-azurestack-upi

/verified by CI

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jan 9, 2026
@openshift-ci-robot
Copy link
Contributor

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

Details

In response to this:

UPI installation succeeded in job e2e-azurestack-upi

/verified by CI

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
Copy link
Contributor

/test e2e-azure-ovn-shared-vpc

@sunku5494
Copy link
Contributor

/retest

@patrickdillon
Copy link
Contributor

/approve
/lgtm
/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Jan 23, 2026
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 23, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 23, 2026

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

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 23, 2026
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD c9de42d and 2 for PR HEAD 3484e2a in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 23, 2026

@openshift-cherrypick-robot: The following tests 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-upi 3484e2a link false /test e2e-azurestack-upi
ci/prow/e2e-azurestack 3484e2a link false /test e2e-azurestack
ci/prow/azure-ovn-marketplace-images 3484e2a link false /test azure-ovn-marketplace-images

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
Copy link
Contributor

/override e2e-azure-ovn-upi

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 27, 2026

@patrickdillon: /override requires failed status contexts, check run or a prowjob name to operate on.
The following unknown contexts/checkruns were given:

  • e2e-azure-ovn-upi

Only the following failed contexts/checkruns were expected:

  • ci/prow/altinfra-images
  • ci/prow/aro-unit
  • ci/prow/artifacts-images
  • ci/prow/azure-ovn-marketplace-images
  • ci/prow/e2e-azure-default-config
  • ci/prow/e2e-azure-ovn
  • ci/prow/e2e-azure-ovn-shared-vpc
  • ci/prow/e2e-azure-ovn-upi
  • ci/prow/e2e-azurestack
  • ci/prow/e2e-azurestack-upi
  • ci/prow/gofmt
  • ci/prow/golint
  • ci/prow/govet
  • ci/prow/images
  • ci/prow/okd-scos-images
  • ci/prow/shellcheck
  • ci/prow/tf-fmt
  • ci/prow/tf-lint
  • ci/prow/unit
  • ci/prow/verify-codegen
  • ci/prow/verify-vendor
  • ci/prow/yaml-lint
  • pull-ci-openshift-installer-fcos-gofmt
  • pull-ci-openshift-installer-fcos-golint
  • pull-ci-openshift-installer-fcos-govet
  • pull-ci-openshift-installer-fcos-images
  • pull-ci-openshift-installer-fcos-unit
  • pull-ci-openshift-installer-fcos-verify-codegen
  • pull-ci-openshift-installer-fcos-verify-vendor
  • pull-ci-openshift-installer-main-artifacts-images
  • pull-ci-openshift-installer-main-azure-ovn-marketplace-images
  • pull-ci-openshift-installer-main-e2e-azure-default-config
  • pull-ci-openshift-installer-main-e2e-azure-ovn
  • pull-ci-openshift-installer-main-e2e-azure-ovn-shared-vpc
  • pull-ci-openshift-installer-main-e2e-azure-ovn-upi
  • pull-ci-openshift-installer-main-e2e-azurestack
  • pull-ci-openshift-installer-main-e2e-azurestack-upi
  • pull-ci-openshift-installer-main-okd-scos-images
  • pull-ci-openshift-installer-main-shellcheck
  • pull-ci-openshift-installer-main-yaml-lint
  • pull-ci-openshift-installer-master-tf-fmt
  • pull-ci-openshift-installer-master-tf-lint
  • pull-ci-openshift-installer-release-4.11-aro-unit
  • pull-ci-openshift-installer-release-4.15-altinfra-images
  • tide

If you are trying to override a checkrun that has a space in it, you must put a double quote on the context.

Details

In response to this:

/override e2e-azure-ovn-upi

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.

@sadasu
Copy link
Contributor

sadasu commented Jan 27, 2026

/override ci/prow/e2e-azure-ovn-upi

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 27, 2026

@sadasu: Overrode contexts on behalf of sadasu: ci/prow/e2e-azure-ovn-upi

Details

In response to this:

/override ci/prow/e2e-azure-ovn-upi

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-merge-bot openshift-merge-bot bot merged commit 9e0603b into openshift:release-4.18 Jan 27, 2026
20 of 23 checks passed
@openshift-ci-robot
Copy link
Contributor

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

/assign jinyunma

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.

@sunku5494
Copy link
Contributor

/cherry-pick release-4.17

@openshift-cherrypick-robot
Copy link
Author

@sunku5494: new pull request created: #10264

Details

In response to this:

/cherry-pick release-4.17

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.

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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. 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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants