OCPBUGS-64842: Disable LoadBalancer in cloud config when Octavia is unavailable#10326
Conversation
stephenfin
left a comment
There was a problem hiding this comment.
I think this approach makes sense. One vaguely-related comment inline
|
/retest |
1 similar comment
|
/retest |
2d03a44 to
91529ff
Compare
…ilable When Octavia (load-balancer) endpoint is not available in the OpenStack service catalog, explicitly set [LoadBalancer] enabled = false in the cloud provider config. This prevents the Cloud Controller Manager from crashing on startup due to an upstream change in cloud-provider-openstack that changed error handling from klog.Errorf to klog.Fatalf when the LoadBalancer client cannot be created. The fix uses the same pattern already established in the cluster destroy code (pkg/destroy/openstack/openstack.go) to detect Octavia availability by checking for gophercloud.ErrEndpointNotFound. Fixes: https://issues.redhat.com/browse/OCPBUGS-64842 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
91529ff to
340389a
Compare
|
/retest |
|
/test e2e-openstack-proxy |
|
/test e2e-openstack-ovn |
|
/approve |
|
The CI failure was due to |
|
/jira refresh |
|
@eshulman2: No Jira issue is referenced in the title of this pull request. DetailsIn 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. |
|
@eshulman2: This pull request references Jira Issue OCPBUGS-64842, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn 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 |
|
@eshulman2: This pull request references Jira Issue OCPBUGS-64842, which is valid. 3 validation(s) were run on this bug
DetailsIn 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. |
|
@mandre: mandre 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. DetailsIn 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. |
|
OK, let's give the e2e-openstack-proxy job one more chance before we ask someone else to override. |
|
/verified later eshulman |
|
/test e2e-openstack-proxy |
|
/verified later eshulman |
|
@mandre: Only users can be targets for the DetailsIn 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. |
|
/verified later @eshulman2 |
|
@mandre: This PR has been marked to be verified later by DetailsIn 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-openstack-ovn |
|
override due to known etcd infrastructure issue |
|
@patrickdillon: Overrode contexts on behalf of patrickdillon: ci/prow/e2e-openstack-ovn DetailsIn 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 gofmt govet unit verify-deps yaml-lint |
|
/override ci/prow/okd-scos-images unrelated infra issue |
|
@patrickdillon: Overrode contexts on behalf of patrickdillon: ci/prow/okd-scos-images DetailsIn 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. |
|
@eshulman2: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
@eshulman2: Jira Issue OCPBUGS-64842: All pull requests linked via external trackers have merged: This pull request has the DetailsIn 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 cherrypick release-4.21,release-4.20 |
1 similar comment
|
/jira cherrypick release-4.21,release-4.20 |
|
/cherrypick release-4.21,release-4.20 |
|
@eshulman2: cannot checkout DetailsIn 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. |
|
/cherrypick release-4.21 |
|
/cherrypick release-4.20 |
|
@eshulman2: new pull request created: #10399 DetailsIn 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. |
|
@eshulman2: #10326 failed to apply on top of branch "release-4.20": DetailsIn 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. |
When Octavia (load-balancer) endpoint is not available in the OpenStack service catalog, explicitly set [LoadBalancer] enabled = false in the cloud provider config. This prevents the Cloud Controller Manager from crashing on startup due to an upstream change in cloud-provider-openstack that changed error handling from klog.Errorf to klog.Fatalf when the LoadBalancer client cannot be created.
The fix uses the same pattern already established in the cluster destroy code (pkg/destroy/openstack/openstack.go) to detect Octavia availability by checking for gophercloud.ErrEndpointNotFound.
related to: https://issues.redhat.com/browse/OCPBUGS-64842
Summary by CodeRabbit
Release Notes