Skip to content
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

OCPBUGS-51090: Fix panic for GetZoneByNodeName on Azure Stack #141

Merged

Conversation

patrickdillon
Copy link

Azure Stack does not support the API Version, 2020-12-01, for PlatformFaultDomain, and therefore panics when we run the cloud provider on Azure Stack. This avoids the panic, but we cannot get the correct PlatformFaultDomain (which may not be an issue).

@patrickdillon
Copy link
Author

/wip
I will open an upstream issue. Opening this now for testing

@openshift-ci openshift-ci bot requested review from nrb and theobarberbany March 26, 2025 16:59
Azure Stack does not support the API Version, 2020-12-01, for
PlatformFaultDomain, and therefore panics when we run the cloud
provider on Azure Stack. This avoids the panic, but we cannot
get the correct PlatformFaultDomain (which may not be an issue).
@patrickdillon patrickdillon force-pushed the ash-fault-domain-panic branch from b4f27fe to df298c5 Compare March 27, 2025 19:00
@patrickdillon
Copy link
Author

I have confirmed this fixes the panic upstream

Opened issue and pull request upstream:
kubernetes-sigs#8754
kubernetes-sigs#8755

@nrb
Copy link

nrb commented Mar 27, 2025

lgtm, will wait for tests before doing an approve.

Copy link

openshift-ci bot commented Mar 27, 2025

@patrickdillon: all tests passed!

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.

@patrickdillon
Copy link
Author

This has already merged upstream: kubernetes-sigs#8755

So I think it would be best to just pick this up in a rebase.

@nrb
Copy link

nrb commented Apr 11, 2025

@patrickdillon it will be easiest from our side to merge this and then have this carry commit dropped automatically later

@patrickdillon patrickdillon changed the title Fix panic for GetZoneByNodeName on Azure Stack OCPBUGS-51090: Fix panic for GetZoneByNodeName on Azure Stack Apr 11, 2025
@openshift-ci-robot openshift-ci-robot added jira/severity-critical Referenced Jira bug's severity is critical 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 Apr 11, 2025
@openshift-ci-robot
Copy link

@patrickdillon: This pull request references Jira Issue OCPBUGS-51090, which is invalid:

  • expected the bug to target the "4.19.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.

In response to this:

Azure Stack does not support the API Version, 2020-12-01, for PlatformFaultDomain, and therefore panics when we run the cloud provider on Azure Stack. This avoids the panic, but we cannot get the correct PlatformFaultDomain (which may not be an issue).

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

patrickdillon commented Apr 11, 2025

/jira refresh

@nrb
Copy link

nrb commented Apr 11, 2025

/lgtm
/approve

@patrickdillon
Copy link
Author

/jira refresh

fat fingers

@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 Apr 11, 2025
@openshift-ci-robot
Copy link

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

Requesting review from QA contact:
/cc @sunzhaohua2

In response to this:

/jira refresh

fat fingers

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 sunzhaohua2 April 11, 2025 15:20
@nrb
Copy link

nrb commented Apr 11, 2025

/tide refresh

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 11, 2025
Copy link

openshift-ci bot commented Apr 11, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nrb

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 /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 Apr 11, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 8e579f3 into openshift:main Apr 11, 2025
11 checks passed
@openshift-ci-robot
Copy link

@patrickdillon: Jira Issue OCPBUGS-51090: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-51090 has been moved to the MODIFIED state.

In response to this:

Azure Stack does not support the API Version, 2020-12-01, for PlatformFaultDomain, and therefore panics when we run the cloud provider on Azure Stack. This avoids the panic, but we cannot get the correct PlatformFaultDomain (which may not be an issue).

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

[ART PR BUILD NOTIFIER]

Distgit: ose-azure-cloud-controller-manager
This PR has been included in build ose-azure-cloud-controller-manager-container-v4.19.0-202504111744.p0.g8e579f3.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

Distgit: ose-azure-cloud-node-manager
This PR has been included in build ose-azure-cloud-node-manager-container-v4.19.0-202504111744.p0.g8e579f3.assembly.stream.el9.
All builds following this will include this PR.

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. jira/severity-critical Referenced Jira bug's severity is critical 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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants