Bug 1795227 - OperatorGroup shoudn't be created when CONTENT_ONLY variable is set
Summary: OperatorGroup shoudn't be created when CONTENT_ONLY variable is set
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Installation
Version: 2.2.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 2.3.0
Assignee: Simone Tiraboschi
QA Contact: Irina Gulina
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-01-27 13:37 UTC by Irina Gulina
Modified: 2020-05-28 09:41 UTC (History)
3 users (show)

Fixed In Version: 2.3
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-04 19:10:37 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github kubevirt hyperconverged-cluster-operator pull 415 0 None closed Skip OperatorGroup creation with CONTENT_ONLY option 2020-05-28 09:35:40 UTC
Red Hat Product Errata RHEA-2020:2011 0 None None None 2020-05-04 19:10:49 UTC

Description Irina Gulina 2020-01-27 13:37:09 UTC
Description of problem:

When using CNV install scripts, marketplace-qe-testing and deploy_marketplace, for CONTENT_ONLY non empty variable, the OperatorGroup shoudn't be created. Otherwise, UI displays "Namespace doesn't support install modes for this Operator" error.


Version-Release number of selected component (if applicable):
CNV 2.2 on OCP 4.3
CNV 2.3

How reproducible:
always

Steps to Reproduce:
0. oc patch OperatorHub cluster --type json  -p '[{"op": "add", "path": "/spec/disableAllDefaultSources", "value": true}]'
1. execute marketplace-qe-testing or deploy_marketplace scripts with CONTENT_ONLY=true
2. go to UI, try to complete the installation from OperatorHub, by finding CNV icon, clicking it and so on. 
3.

Actual results:
"Namespace doesn't support install modes for this Operator" error.

Expected results:
successful installation

Comment 2 Nelly Credi 2020-02-17 08:19:27 UTC
Please add fixed in version

Comment 6 errata-xmlrpc 2020-05-04 19:10:37 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, 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/RHEA-2020:2011

Comment 7 Simone Tiraboschi 2020-05-28 09:41:29 UTC
Removing old need info.


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