-
Notifications
You must be signed in to change notification settings - Fork 1.5k
MULTIARCH-5817: Upgrade az version in upi-installer image to fix 'az sig image-version create' issue #10067
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
/retest |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sadasu The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest |
|
/test e2e-gcp-ovn-upi |
|
/test ? |
|
@jinyunma: The following commands are available to trigger required jobs: The following commands are available to trigger optional jobs: Use In 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 kubernetes-sigs/prow repository. |
|
/test e2e-azurestack-upi |
|
@lwan-wanglin: This pull request explicitly references no jira issue. In 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. |
|
/test e2e-azurestack-upi /test e2e-azure-ovn-upi |
|
/lgtm |
|
@lwan-wanglin: This pull request references MULTIARCH-5817 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.21.0" version, but no target version was set. In 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. |
|
/override ci/prow/e2e-gcp-ovn-upi |
|
@lwan-wanglin: lwan-wanglin unauthorized: /override is restricted to Repo administrators, approvers in top level OWNERS file, and the following github teams:openshift: openshift-release-oversight openshift-staff-engineers openshift-sustaining-engineers. In 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 kubernetes-sigs/prow repository. |
|
/verified by @lwan-wanglin, @jinyunma |
|
@lwan-wanglin: This PR has been marked as verified by In 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. |
|
@lwan-wanglin: The following tests failed, say
Full PR test history. Your PR dashboard. 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. |
|
Hi @sadasu, could you help override the “ci/prow/e2e-gcp-ovn-upi” job? The failure is unrelated to the changes, and I’ve already verified the Azure command part. Thank you! |
we encountered an issue in the Prow CI
ipi-install-heterogeneousstep when runningaz sig image-version create(see the below error message). It is related to issue #30942 in the Azure CLI, and the fix is included starting in version v2.72.0. the current version inupi-installerimage(introduced byquay.io/ocp-splat/pwsh:v7.3.12) is v2.61.0.Joseph Callen has rebuilt the image with the latest Azure CLI version and pushed it to
quay.io/ocp-splat/pwsh:latest, Therefore, we need to update the Dockerfile accordingly.