1782948 – NFD pods disappear after cluster upgrade

Bug 1782948 - NFD pods disappear after cluster upgrade

Summary: NFD pods disappear after cluster upgrade

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Node Feature Discovery Operator
Sub Component:
Version:	4.4
Hardware:	Unspecified
OS:	Unspecified
Priority:	unspecified
Severity:	high
Target Milestone:	---
Target Release:	4.4.0
Assignee:	Zvonko Kosic
QA Contact:	Eric Matysek
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:	1775849 1785307
TreeView+	depends on / blocked

Reported:	2019-12-12 16:58 UTC by Zvonko Kosic
Modified:	2020-05-04 11:20 UTC (History)
CC List:	5 users (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:	1775849
Environment:
Last Closed:	2020-05-04 11:19:53 UTC
Target Upstream Version:

Attachments	(Terms of Use)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Github	openshift cluster-nfd-operator pull 45	0	None	closed	Bug 1782948: Added more Watcher for secondary resource	2020-03-02 21:36:40 UTC
Red Hat Product Errata	RHBA-2020:0581	0	None	None	None	2020-05-04 11:20:27 UTC

Comment 2 Zvonko Kosic 2020-02-07 14:46:33 UTC

Any update on this BZ?

Comment 3 Walid A. 2020-02-14 20:10:10 UTC

Verified that nfd pods did not disappear after upgrade from OCP 4.3.1 to 4.4.0-0.nightly-2020-02-13-124128.

Server Version: 4.4.0-0.nightly-2020-02-13-124128
Kubernetes Version: v1.17.1

# oc adm upgrade status
Cluster version is 4.4.0-0.nightly-2020-02-13-124128

No updates available. You may force an upgrade to a specific release image, but doing so may not be supported and result in downtime or data loss.

# oc get co
NAME                                       VERSION                             AVAILABLE   PROGRESSING   DEGRADED   SINCE
authentication                             4.4.0-0.nightly-2020-02-13-124128   True        False         False      3d4h
cloud-credential                           4.4.0-0.nightly-2020-02-13-124128   True        False         False      3d4h
cluster-autoscaler                         4.4.0-0.nightly-2020-02-13-124128   True        False         False      3d4h
console                                    4.4.0-0.nightly-2020-02-13-124128   True        False         False      5h28m
csi-snapshot-controller                    4.4.0-0.nightly-2020-02-13-124128   True        False         False      5h41m
dns                                        4.4.0-0.nightly-2020-02-13-124128   True        False         False      3d4h
etcd                                       4.4.0-0.nightly-2020-02-13-124128   True        False         False      5h18m
image-registry                             4.4.0-0.nightly-2020-02-13-124128   True        False         False      5h25m
ingress                                    4.4.0-0.nightly-2020-02-13-124128   True        False         False      5h25m
insights                                   4.4.0-0.nightly-2020-02-13-124128   True        False         False      3d4h
kube-apiserver                             4.4.0-0.nightly-2020-02-13-124128   True        False         False      6h8m
kube-controller-manager                    4.4.0-0.nightly-2020-02-13-124128   True        False         False      6h7m
kube-scheduler                             4.4.0-0.nightly-2020-02-13-124128   True        False         False      6h7m
kube-storage-version-migrator              4.4.0-0.nightly-2020-02-13-124128   True        False         False      5h25m
machine-api                                4.4.0-0.nightly-2020-02-13-124128   True        False         False      3d4h
machine-config                             4.4.0-0.nightly-2020-02-13-124128   True        False         False      5h18m
marketplace                                4.4.0-0.nightly-2020-02-13-124128   True        False         False      5h27m
monitoring                                 4.4.0-0.nightly-2020-02-13-124128   True        False         False      5h40m
network                                    4.4.0-0.nightly-2020-02-13-124128   True        False         False      3d4h
node-tuning                                4.4.0-0.nightly-2020-02-13-124128   True        False         False      6h
openshift-apiserver                        4.4.0-0.nightly-2020-02-13-124128   True        False         False      5h21m
openshift-controller-manager               4.4.0-0.nightly-2020-02-13-124128   True        False         False      3d4h
openshift-samples                          4.4.0-0.nightly-2020-02-13-124128   True        False         False      6h1m
operator-lifecycle-manager                 4.4.0-0.nightly-2020-02-13-124128   True        False         False      3d4h
operator-lifecycle-manager-catalog         4.4.0-0.nightly-2020-02-13-124128   True        False         False      3d4h
operator-lifecycle-manager-packageserver   4.4.0-0.nightly-2020-02-13-124128   True        False         False      5h23m
service-ca                                 4.4.0-0.nightly-2020-02-13-124128   True        False         False      3d4h
service-catalog-apiserver                  4.4.0-0.nightly-2020-02-13-124128   True        False         False      3d4h
service-catalog-controller-manager         4.4.0-0.nightly-2020-02-13-124128   True        False         False      3d4h
storage                                    4.4.0-0.nightly-2020-02-13-124128   True        False         False      6h


# oc get pods -n openshift-nfd
NAME                           READY   STATUS    RESTARTS   AGE
nfd-master-4m5s4               1/1     Running   0          2d17h
nfd-master-jrs72               1/1     Running   0          2d17h
nfd-master-pz9dh               1/1     Running   0          2d17h
nfd-operator-f77bc847f-wn7j9   1/1     Running   0          5h28m
nfd-worker-64mwk               1/1     Running   2          2d17h
nfd-worker-9phjq               1/1     Running   0          2d17h
nfd-worker-zn78b               1/1     Running   1          2d17h

Comment 4 Walid A. 2020-02-14 20:11:20 UTC

Verified after upgrade from OCP 4.3.1 to 4.4.0-0.nightly-2020-02-13-124128.

Comment 6 errata-xmlrpc 2020-05-04 11:19:53 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/RHBA-2020:0581

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