Bug 2086432

+++ This bug was initially created as a clone of Bug #2084732 +++

Description of problem:
Deleting a special resource in OCP 4.10 hangs if the SR was created in 4.9 and went through an upgrade. When calling "oc delete sr/simple-kmod" from the CLI - the call never returns, and the resource and the created daemonset and pods etc' are never removed. In the log you see "Marked to be deleted" and it also looks like the reconciliation finished:

INFO    reconcile: UPDATE       Reconciling SpecialResource(s) in all Namespaces
INFO    reconcile: UPDATE       Marked to be deleted, reconciling finalizer
INFO    cache   Nodes cached    {"name": "worker-0-0"}
INFO    cache   Nodes cached    {"name": "worker-0-1"}
INFO    cache   Nodes cached    {"name": "worker-0-2"}
INFO    cache   Node list:      {"length": 3}   
INFO    cache   Nodes   {"num": 3}
INFO    warning         OnError: node Conflict Label specialresource.openshift.io/state-simple-kmod-1000 err %!s(<nil>)  
INFO    reconcile: UPDATE       Successfully finalized  {"SpecialResource:": "simple-kmod"}
INFO    status          Reconciling ClusterOperator     
INFO    status          Adding to relatedObjects        {"namespace": "simple-kmod"}
INFO    status          RECONCILE SUCCESS: Reconcile

This is because finalizers were changed between 4.9 and 4.10, and the finalizer from 4.9 is never removed since SRO in 4.10 is not aware of it.


Version-Release number of selected component (if applicable):
OCP 4.9 -> 4.10


How reproducible:
probably 100%


Steps to Reproduce:
1. Install OCP 4.9, and install NFD and SRO from OLM
2. Deploy the simple-kmod example
3. Upgrade to the latest 4.10
4. oc delete sr/simple-kmod


Actual results:
The SR is never deleted


Expected results:
The SR and all related resources should be removed