Skip to content

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

Merged
openshift-merge-bot[bot] merged 3 commits intoopenshift:mainfrom
eshulman2:fix-ocpbugs-64842
Mar 16, 2026
Merged

OCPBUGS-64842: Disable LoadBalancer in cloud config when Octavia is unavailable#10326
openshift-merge-bot[bot] merged 3 commits 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

Summary by CodeRabbit

Release Notes

  • New Features
    • Enhanced OpenStack Octavia load balancer service detection to automatically configure load balancer support based on availability
    • Added PowerVC platform support with appropriate configuration handling

@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

@stephenfin
Copy link
Contributor

/approve
/lgtm

@openshift-ci openshift-ci bot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels 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.

@eshulman2
Copy link
Member Author

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@eshulman2: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

Details

In response to this:

/jira refresh

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 eshulman2 changed the title OCPBUGS-64842 openstack: Disable LoadBalancer in cloud config when Octavia is unavailable OCPBUGS-64842: Disable LoadBalancer in cloud config when Octavia is unavailable Mar 4, 2026
@openshift-ci-robot openshift-ci-robot added 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 Mar 4, 2026
@openshift-ci-robot
Copy link
Contributor

@eshulman2: This pull request references Jira Issue OCPBUGS-64842, which is invalid:

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

Details

In response to this:

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

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

/jira refresh

@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 Mar 4, 2026
@openshift-ci-robot
Copy link
Contributor

@eshulman2: This pull request references Jira Issue OCPBUGS-64842, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.22.0) matches configured target version for branch (4.22.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
Details

In response to this:

/jira refresh

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 removed the lgtm Indicates that a PR is ready to be merged. label Mar 8, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 16, 2026

@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.

Details

In response to this:

/override ci/prow/e2e-openstack-ovn

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.

@mandre
Copy link
Member

mandre commented Mar 16, 2026

OK, let's give the e2e-openstack-proxy job one more chance before we ask someone else to override.
/retest-required

@mandre
Copy link
Member

mandre commented Mar 16, 2026

/verified later eshulman

@eshulman2
Copy link
Member Author

/test e2e-openstack-proxy

@mandre
Copy link
Member

mandre commented Mar 16, 2026

/verified later eshulman

@openshift-ci-robot
Copy link
Contributor

@mandre: Only users can be targets for the /verified later command.

Details

In response to this:

/verified later eshulman

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

mandre commented Mar 16, 2026

/verified later @eshulman2

@openshift-ci-robot openshift-ci-robot added verified-later verified Signifies that the PR passed pre-merge verification criteria labels Mar 16, 2026
@openshift-ci-robot
Copy link
Contributor

@mandre: This PR has been marked to be verified later by @eshulman2.

Details

In response to this:

/verified later @eshulman2

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
Contributor

/override ci/prow/e2e-openstack-ovn

@patrickdillon
Copy link
Contributor

override due to known etcd infrastructure issue

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 16, 2026

@patrickdillon: Overrode contexts on behalf of patrickdillon: ci/prow/e2e-openstack-ovn

Details

In response to this:

/override ci/prow/e2e-openstack-ovn

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.

@tthvo
Copy link
Member

tthvo commented Mar 16, 2026

/test gofmt govet unit verify-deps yaml-lint

@patrickdillon
Copy link
Contributor

/override ci/prow/okd-scos-images

unrelated infra issue

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 16, 2026

@patrickdillon: Overrode contexts on behalf of patrickdillon: ci/prow/okd-scos-images

Details

In response to this:

/override ci/prow/okd-scos-images

unrelated infra 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 kubernetes-sigs/prow repository.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 16, 2026

@eshulman2: all tests passed!

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.

@openshift-merge-bot openshift-merge-bot bot merged commit b3e61d0 into openshift:main Mar 16, 2026
19 checks passed
@openshift-ci-robot
Copy link
Contributor

@eshulman2: Jira Issue OCPBUGS-64842: All pull requests linked via external trackers have merged:

This pull request has the verified-later tag and will need to be manually moved to VERIFIED after testing. Jira Issue OCPBUGS-64842 has been moved to the MODIFIED state.

Details

In response to this:

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

  • New Features
  • Enhanced OpenStack Octavia load balancer service detection to automatically configure load balancer support based on availability
  • Added PowerVC platform support with appropriate configuration handling

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

mandre commented Mar 17, 2026

/jira cherrypick release-4.21,release-4.20

1 similar comment
@eshulman2
Copy link
Member Author

/jira cherrypick release-4.21,release-4.20

@eshulman2 eshulman2 deleted the fix-ocpbugs-64842 branch March 17, 2026 08:07
@eshulman2
Copy link
Member Author

/cherrypick release-4.21,release-4.20

@openshift-cherrypick-robot

@eshulman2: cannot checkout release-4.21,release-4.20: error checking out "release-4.21,release-4.20": exit status 1 error: pathspec 'release-4.21,release-4.20' did not match any file(s) known to git

Details

In response to this:

/cherrypick release-4.21,release-4.20

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

/cherrypick release-4.21

@eshulman2
Copy link
Member Author

/cherrypick release-4.20

@openshift-cherrypick-robot

@eshulman2: new pull request created: #10399

Details

In response to this:

/cherrypick release-4.21

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.

@openshift-cherrypick-robot

@eshulman2: #10326 failed to apply on top of branch "release-4.20":

Applying: openstack: Disable LoadBalancer in cloud config when Octavia is unavailable
Using index info to reconstruct a base tree...
M	pkg/asset/manifests/openstack/cloudproviderconfig.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/asset/manifests/openstack/cloudproviderconfig.go
CONFLICT (content): Merge conflict in pkg/asset/manifests/openstack/cloudproviderconfig.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0001 openstack: Disable LoadBalancer in cloud config when Octavia is unavailable

Details

In response to this:

/cherrypick release-4.20

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.

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/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. verified Signifies that the PR passed pre-merge verification criteria verified-later

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants