Bug 1908492

Summary:	OCP 4.7: Node Feature Discovery (NFD) Operator Custom Resource Definition file in olm-catalog is not in sync with the one in manifests dir leading to failed deployment from OperatorHub
Product:	OpenShift Container Platform	Reporter:	Walid A. <wabouham>
Component:	Node Feature Discovery Operator	Assignee:	Carlos Eduardo Arango Gutierrez <carangog>
Status:	CLOSED ERRATA	QA Contact:	Walid A. <wabouham>
Severity:	high	Docs Contact:
Priority:	medium
Version:	4.7	CC:	carangog, mifiedle, rpattath, scuppett, sejug
Target Milestone:	---	Flags:	carangog: needinfo-
Target Release:	4.7.0
Hardware:	x86_64
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-02-24 15:01:39 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 Walid A. 2020-12-16 20:52:05 UTC

Description of problem:
NFD Operator CustomResourceDefinition under OLM catalog is out of sync  with CRD in the  manifests dir leading to operator deployment failure when installing via OperatorHub.  

Files that are not in sync:

OLM catalog:
 https://github.com/openshift/cluster-nfd-operator/blob/master/manifests/olm-catalog/4.7/nfd.crd.yaml


Manifests dir: https://github.com/openshift/cluster-nfd-operator/blob/master/manifests/0500_crd.yaml

Version-Release number of selected component (if applicable):
Client Version: 4.7.0-0.nightly-2020-12-14-165231
Server Version: 4.7.0-0.nightly-2020-12-14-165231
Kubernetes Version: v1.19.2+e386040


How reproducible:
Always

Steps to Reproduce:
1. Create an IPI OCP 4.7 cluster on AWS, 3 master and 3 worker nodes.  Use our Flexy automation which creates a catalogesource for qe-app-registry to pull latest NFD images.
2. From Console create a new project called "test-nfd"
3. From Console, Operator -> OperatorHub, search for NFD operator and install it in test-nfd namespace just created
  - Update Channel:  4.7, Approval Strategy Automatic
4.  Wait for operator status to show Succeeded


Actual results:
NFD operator staus stuck in Pending state

Expected results:
nfd operator running, and Status on console should show Succeeded


Additional info:

Comment 3 Walid A. 2020-12-18 21:26:02 UTC

Failed verification on OCP 4.7.0-0.nightly-2020-12-18-031435.

NFD Operator is stuck in "Upgrade Pending" state when deployed from OperatorHub of the OpenShift console.

OCP version:  4.7.0-0.nightly-2020-12-18-031435 

NFD Operator version:  4.7.0-202012171720.p0

# oc get catalogsource -n openshift-marketplace
NAME                  DISPLAY                TYPE   PUBLISHER      AGE
certified-operators   Certified Operators    grpc   Red Hat        6h49m
community-operators   Community Operators    grpc   Red Hat        6h49m
qe-app-registry       Production Operators   grpc   OpenShift QE   6h26m
redhat-marketplace    Red Hat Marketplace    grpc   Red Hat        6h49m
redhat-operators      Red Hat Operators      grpc   Red Hat        6h49m

# oc get packagemanifest -l catalog=qe-app-registry
NAME                                CATALOG                AGE
cluster-logging                     Production Operators   6h28m
compliance-operator                 Production Operators   6h28m
elasticsearch-operator              Production Operators   6h28m
ptp-operator                        Production Operators   6h28m
metering-ocp                        Production Operators   6h28m
cluster-kube-descheduler-operator   Production Operators   6h28m
local-storage-operator              Production Operators   6h28m
nfd                                 Production Operators   6h28m
sriov-network-operator              Production Operators   6h28m
amq-streams                         Production Operators   6h28m

Comment 5 Walid A. 2021-01-26 14:49:57 UTC

Verified on OCP 4.7.0-0.nightly-2021-01-22-134922.

Comment 7 errata-xmlrpc 2021-02-24 15:01:39 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 Container Platform 4.7.0 extras and security 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-2020:5635