Skip to content

Commit

Permalink
OCPBUGS-32776: Add Missing Scope Change Instructions on PowerVS
Browse files Browse the repository at this point in the history
The instructions for effectuating a scope change were missing because
the `loadBalancerServiceIsProgressing` did not account for the PowerVS
Platform Type. This update add those instructions for PowerVS users
when they change an IngressController's scope.
  • Loading branch information
gcs278 committed Aug 26, 2024
1 parent b07d602 commit 0716651
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion pkg/operator/controller/ingress/load_balancer_service.go
Original file line number Diff line number Diff line change
Expand Up @@ -794,7 +794,7 @@ func loadBalancerServiceIsProgressing(ic *operatorv1.IngressController, service
if wantScope != haveScope {
err := fmt.Errorf("The IngressController scope was changed from %q to %q.", haveScope, wantScope)
switch platform.Type {
case configv1.AWSPlatformType, configv1.IBMCloudPlatformType:
case configv1.AWSPlatformType, configv1.IBMCloudPlatformType, configv1.PowerVSPlatformType:
err = fmt.Errorf("%[1]s To effectuate this change, you must delete the service: `oc -n %[2]s delete svc/%[3]s`; the service load-balancer will then be deprovisioned and a new one created. This will most likely cause the new load-balancer to have a different host name and IP address from the old one's. Alternatively, you can revert the change to the IngressController: `oc -n openshift-ingress-operator patch ingresscontrollers/%[4]s --type=merge --patch='{\"spec\":{\"endpointPublishingStrategy\":{\"loadBalancer\":{\"scope\":\"%[5]s\"}}}}'`", err.Error(), service.Namespace, service.Name, ic.Name, haveScope)
}
errs = append(errs, err)
Expand Down

0 comments on commit 0716651

Please sign in to comment.