Bug 2100180

Summary: Upgrading the MetalLB Operator to 4.11 version fails
Product: OpenShift Container Platform Reporter: Federico Paolinelli <fpaoline>
Component: NetworkingAssignee: Federico Paolinelli <fpaoline>
Networking sub component: Metal LB QA Contact: Arti Sood <asood>
Status: CLOSED CURRENTRELEASE Docs Contact: kquinn
Severity: medium    
Priority: medium CC: cgoncalves
Version: 4.11   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Known Issue
Doc Text:
Cause: Changing the operator scope from namespace to cluster doesn't allow migrating from a version to another. Consequence: Upgrade from a prior version will not succeed. Workaround (if any): Remove the previous version of the operator (without deleting the namespace nor the instance of the MetalLB CR), and deploy the new one will keep metallb running and configured. Result:
 Story Points: ---
Clone Of: Environment:
Last Closed: 2023-02-10 10:30:33 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Federico Paolinelli 2022-06-22 16:31:20 UTC 
Description of problem:

Due to the fact that the metallb operator scope is changing from namespaced to cluster, upgrading will fail

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Deploy the 4.10 or previous version of the operator
2. Upgrade to 4.11
3.

Actual results:


Expected results:


Additional info:
Comment 7 Carlos Goncalves 2023-02-10 10:30:33 UTC 
Known issue added to 4.11 release notes
https://docs.openshift.com/container-platform/4.11/release_notes/ocp-4-11-release-notes.html#ocp-4-11-known-issues