-
Notifications
You must be signed in to change notification settings - Fork 18
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
OCPBUGS-51090: Fix panic for GetZoneByNodeName on Azure Stack #141
Conversation
/wip |
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).
b4f27fe
to
df298c5
Compare
I have confirmed this fixes the panic upstream Opened issue and pull request upstream: |
lgtm, will wait for tests before doing an approve. |
@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. |
This has already merged upstream: kubernetes-sigs#8755 So I think it would be best to just pick this up in a rebase. |
@patrickdillon it will be easiest from our side to merge this and then have this carry commit dropped automatically later |
@patrickdillon: This pull request references Jira Issue OCPBUGS-51090, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. 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. |
/jira refresh |
/lgtm |
/jira refresh fat fingers |
@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
Requesting review from QA contact: 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. |
/tide refresh |
[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 |
@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:
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. |
[ART PR BUILD NOTIFIER] Distgit: ose-azure-cloud-controller-manager |
[ART PR BUILD NOTIFIER] Distgit: ose-azure-cloud-node-manager |
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).