Skip to content

OCPBUGS-64842 openstack: Disable LoadBalancer in cloud config when Octavia is unavailable#10326

Open
eshulman2 wants to merge 1 commit intoopenshift:mainfrom
eshulman2:fix-ocpbugs-64842
Open

OCPBUGS-64842 openstack: Disable LoadBalancer in cloud config when Octavia is unavailable#10326
eshulman2 wants to merge 1 commit intoopenshift:mainfrom
eshulman2:fix-ocpbugs-64842

Conversation

@eshulman2
Copy link
Member

@eshulman2 eshulman2 commented Feb 23, 2026

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

@openshift-ci openshift-ci bot requested review from mandre and stephenfin February 23, 2026 09:34
Copy link
Contributor

@stephenfin stephenfin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this approach makes sense. One vaguely-related comment inline

@eshulman2
Copy link
Member Author

/retest

1 similar comment
@eshulman2
Copy link
Member Author

/retest

…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>
@eshulman2
Copy link
Member Author

/retest

@eshulman2 eshulman2 changed the title openstack: Disable LoadBalancer in cloud config when Octavia is unavailable OCPBUGS-64842 openstack: Disable LoadBalancer in cloud config when Octavia is unavailable Feb 25, 2026
@eshulman2
Copy link
Member Author

/test e2e-openstack-proxy

@eshulman2
Copy link
Member Author

/test e2e-openstack-ovn

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 26, 2026

@eshulman2: The following test 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-openstack-ovn 340389a link true /test e2e-openstack-ovn

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.

@stephenfin
Copy link
Contributor

/approve
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 26, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 26, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: stephenfin

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 Feb 26, 2026
@stephenfin
Copy link
Contributor

The CI failure was due to [Monitor:legacy-test-framework-invariants-alerts][bz-etcd][invariant] alert/etcdMemberCommunicationSlow should not be at or above info. That's just slow disk on the cloud we're using.

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. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants