Bug 1801472 - OCP 4.2.18 Stage - Update Channel for NFD Operator needs to default to ver 4.2 when deploying operator from OperatorHub
Summary: OCP 4.2.18 Stage - Update Channel for NFD Operator needs to default to ver 4....
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node Feature Discovery Operator
Version: 4.2.z
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
: 4.6.0
Assignee: Carlos Eduardo Arango Gutierrez
QA Contact: Walid A.
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-10 23:06 UTC by Walid A.
Modified: 2020-09-09 11:49 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-09-09 11:49:04 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Walid A. 2020-02-10 23:06:11 UTC
Description of problem:

This is observed on OCP 4.2.18 stage UPI cluster.  When trying to deploy NFD operator from OperatorHub, the default Update Channel is set to 4.3.  If that's not changed to 4.2, NFD operator fails to deploy successfully.

To avoid confusion, and to ensure successful deploy on first attempt, the default Update Channel needs to be 4.2 on that release.

Error in nfd-operator logs seen when update channel is set to 4.3:

{"level":"info","ts":1581374288.2745879,"logger":"cmd","msg":"Go Version: go1.12.12"}
{"level":"info","ts":1581374288.2746959,"logger":"cmd","msg":"Go OS/Arch: linux/amd64"}
{"level":"info","ts":1581374288.2747009,"logger":"cmd","msg":"Version of operator-sdk: v0.4.0+git"}
{"level":"info","ts":1581374288.2751555,"logger":"leader","msg":"Trying to become the leader."}
{"level":"info","ts":1581374288.37019,"logger":"leader","msg":"Found existing lock with my name. I was likely restarted."}
{"level":"info","ts":1581374288.3702562,"logger":"leader","msg":"Continuing as the leader."}
{"level":"info","ts":1581374288.455795,"logger":"cmd","msg":"Registering Components."}
{"level":"info","ts":1581374288.4561057,"logger":"kubebuilder.controller","msg":"Starting EventSource","controller":"nodefeaturediscovery-controller","source":"kind source: /, Kind="}
{"level":"info","ts":1581374288.4563096,"logger":"kubebuilder.controller","msg":"Starting EventSource","controller":"nodefeaturediscovery-controller","source":"kind source: /, Kind="}
{"level":"info","ts":1581374288.4564064,"logger":"kubebuilder.controller","msg":"Starting EventSource","controller":"nodefeaturediscovery-controller","source":"kind source: /, Kind="}
{"level":"info","ts":1581374288.4564939,"logger":"kubebuilder.controller","msg":"Starting EventSource","controller":"nodefeaturediscovery-controller","source":"kind source: /, Kind="}
{"level":"info","ts":1581374288.456571,"logger":"kubebuilder.controller","msg":"Starting EventSource","controller":"nodefeaturediscovery-controller","source":"kind source: /, Kind="}
{"level":"error","ts":1581374288.4565969,"logger":"cmd","msg":"","error":"no kind is registered for the type v1.SecurityContextConstraints in scheme \"k8s.io/client-go/kubernetes/scheme/register.go:60\"","stacktrace":"github.com/openshift/cluster-nfd-operator/vendor/github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/src/github.com/openshift/cluster-nfd-operator/vendor/github.com/go-logr/zapr/zapr.go:128\nmain.main\n\t/go/src/github.com/openshift/cluster-nfd-operator/cmd/manager/main.go:92\nruntime.main\n\t/opt/rh/go-toolset-1.12/root/usr/lib/go-toolset-1.12-golang/src/runtime/proc.go:200"}


This has been reported in:
https://bugzilla.redhat.com/show_bug.cgi?id=1793535

Version-Release number of selected component (if applicable):
Server Version: 4.2.0-0.nightly-2020-02-10-063139
Kubernetes Version: v1.14.6+ba051ac


How reproducible:
Every time

Steps to Reproduce:
1. UPI install of OCP 4.2.18 on openstack, 2 worker nodes and 3 masters
2. From OpenShift console logged in as kubeadmin, with kubeadmin password from install
3. Create namespace called test-nfd
4. Operators -> OperatorHub, search for NFD operator, click install
5. Default Update channel is set to 4.3, if you change it to 4.2 and proceed with installing NFD operator followed by creating a CSV instance, NFD operator and NFD pods deploy successfully.
6. If take that 4.3 default Update Channel value, and then select test-nfd namespace to install, and proceed with installing NFD operator followed by creating a CSV instance,  NFD operator fails to deploy, pod in CrashLoopbackoff, with operator logs error message:

{"level":"error","ts":1581374288.4565969,"logger":"cmd","msg":"","error":"no kind is registered for the type v1.SecurityContextConstraints in scheme \"k8s.io/client-go/kubernetes/scheme/register.go:60\"","stacktrace":"github.com/openshift/cluster-nfd-operator/vendor/github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/src/github.com/openshift/cluster-nfd-operator/vendor/github.com/go-logr/zapr/zapr.go:128\nmain.main\n\t/go/src/github.com/openshift/cluster-nfd-operator/cmd/manager/main.go:92\nruntime.main\n\t/opt/rh/go-toolset-1.12/root/usr/lib/go-toolset-1.12-golang/src/runtime/proc.go:200"}



Actual results:
NFD operator fails to install when Update channel is left with default value "4.3"


Expected results:
NFD operator install with default Update channel set to 4.2.  Alternatively, release notes could be updated to state that the Update Channel needs to be set to 4.2 and not take the default 4.3 value


Additional info:

Comment 1 Ashley Hardin 2020-02-12 21:44:20 UTC
Documentation update: https://github.com/openshift/openshift-docs/pull/19704

Comment 3 Zvonko Kosic 2020-04-15 18:21:55 UTC
We need to find out what implications this bug has for all releases. Setting to 4.5 target release.

Comment 4 Stephen Cuppett 2020-06-10 11:35:31 UTC
This is not a showstopper for OCP 4.5.0. Setting target release to 4.6.0 (active development branch). For fixes (if any) required/requested on earlier versions of OCP, please create clones targeting 4.5.z and earlier z-stream releases when appropriate.

Comment 5 Carlos Eduardo Arango Gutierrez 2020-08-06 21:09:46 UTC
This bug is a NO-FIX
Why: right now all operators for OpenShift minor versions ship to the exact same content stream, so there just isn't separate metadata for each. this gets fixed in 4.6 when we move to separate content streams per minor OpenShift versions.


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