Bug 2086541 - NMO CSV dependency to CNV is failing
Summary: NMO CSV dependency to CNV is failing
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Installation
Version: 4.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.10.2
Assignee: Oren Cohen
QA Contact: Debarati Basu-Nag
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-16 11:57 UTC by Oren Cohen
Modified: 2022-06-14 17:42 UTC (History)
3 users (show)

Fixed In Version: hco-bundle-registry-container-v4.10.2-5
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-14 17:42:18 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github kubevirt hyperconverged-cluster-operator pull 1942 0 None Merged Revert NMO handling in main 2022-05-27 12:20:57 UTC
Github kubevirt hyperconverged-cluster-operator pull 1946 0 None Merged [release-1.6] Disallow upgrade if NMO is in use, with Upgradable Condition 2022-05-27 12:20:59 UTC
Red Hat Product Errata RHSA-2022:5026 0 None None None 2022-06-14 17:42:25 UTC

Description Oren Cohen 2022-05-16 11:57:11 UTC
Description of problem:
When deploying CNV, starting from v4.11.0-334, node-maintenance-operator is being fetched by OLM according to a dependency set in CNV bundle.

The problem is that NMO supports AllNamespaces InstallMode and doesn't support other InstallModes, while CNV supports only OwnNamespace and SingleNamespace.
Due to this discrepancy, because the OperatorGroup is targeting a single namespace (openshift-cnv), NMO CSV is failed to be installed.

$ oc get csv
NAME                                       DISPLAY                     VERSION   REPLACES                                   PHASE
kubevirt-hyperconverged-operator.v4.11.0   OpenShift Virtualization    4.11.0    kubevirt-hyperconverged-operator.v4.10.0   Succeeded
node-maintenance-operator.v4.10.0          Node Maintenance Operator   4.10.0                                               Failed


Version-Release number of selected component (if applicable):
v4.11.0-334

How reproducible:
100%

Steps to Reproduce:
1. Deploy CNV 4.11.0-334 or later from OSBS.
2.
3.

Actual results:
NMO CSV is failed

Expected results:
see below

Additional info:
Due to this limitation, it has been decided that NMO will still be removed from CNV 4.11 bundle, but it won't be set as a dependency at the OLM level.
If NMO is being used in 4.10.z (i.e. NMO CR(s) exists), HCO will block the upgrade to 4.11 and will raise a descriptive event and upgradeable condition.

temporary W/A to let the NMO CSV be installed in the meanwhile is to patch it to support OwnNamespace InstallMode:
$ oc patch csv node-maintenance-operator.v4.10.0 --patch '{"spec":{"installModes":[{"supported":true,"type":"OwnNamespace"},{"supported":false,"type":"SingleNamespace"},{"supported":false,"type":"MultiNamespace"},{"supported":true,"type":"AllNamespaces"}]}}' --type=merge

Comment 1 Debarati Basu-Nag 2022-06-03 14:41:57 UTC
Verified against v4.11.0-435 via upgrade(4.10.2->4.11.0) and new installation. Post installation and upgrade, no NMO was installed on the cluster, no nmo csv found in error state.

Comment 7 errata-xmlrpc 2022-06-14 17:42:18 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Virtualization 4.10.2 Images security and bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:5026


Note You need to log in before you can comment on or make changes to this bug.