Description of problem:
CNAO at CNV 4.10 running on OCP 4.11 is setting the upgradeable condition to false even if the standalone operator of nmstate is installed (by finding a deployment with app=kubernetes-nmstate-operator label).
it is displaying this message:
NMState deployment is not supported by CNAO anymore, please install Kubernetes NMState Operator

which blocks the upgrade, since it is getting propagated by HCO to OperatorCondition read by OLM.


$ oc get networkaddonsconfigs cluster -o json | jq .status.conditions
[
  {
    "lastTransitionTime": "2022-05-23T22:11:59Z",
    "status": "False",
    "type": "Progressing"
  },
  {
    "lastTransitionTime": "2022-05-23T21:51:58Z",
    "status": "False",
    "type": "Degraded"
  },
  {
    "lastTransitionTime": "2022-05-23T22:11:59Z",
    "status": "True",
    "type": "Available"
  },
  {
    "lastTransitionTime": "2022-05-23T16:16:28Z",
    "message": "NMState deployment is not supported by CNAO anymore, please install Kubernetes NMState Operator",
    "reason": "InvalidConfiguration",
    "status": "False",
    "type": "Upgradeable"
  }
]


$ oc get networkaddonsconfigs cluster -o json | jq .spec
{
  "kubeMacPool": {},
  "linuxBridge": {},
  "multus": {},
  "nmstate": {},
  "selfSignConfiguration": {
    "caOverlapInterval": "24h0m0s",
    "caRotateInterval": "48h0m0s",
    "certOverlapInterval": "12h0m0s",
    "certRotateInterval": "24h0m0s"
  }
}


Version-Release number of selected component (if applicable):
CNV 4.10.2
CNAO 0.65.6

How reproducible:
Always

Steps to Reproduce:
1. Install CNV 4.10 on OCP 4.10
2. Upgrade OCP to 4.11
3. Watch the CNAO upgradable condition

Actual results:
Upgrade to CNV 4.11 is blocked.

Expected results:
CNAO should be satisfied that the nmstate standalone operator is installed and set the upgradeable condition to true.

Additional info:
CNAO checks the existence of "nmstate: {}" in CNAO CR, which is present and can't be removed because it getting reconciled by HCO. CNAO should ignore the nmstate field in the CR.