1986992 – cluster-node-tuning-operator needs to handle API server downtime gracefully in SNO

Bug 1986992 - cluster-node-tuning-operator needs to handle API server downtime gracefully in SNO

Summary: cluster-node-tuning-operator needs to handle API server downtime gracefully i...

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Node Tuning Operator
Sub Component:
Version:	4.9
Hardware:	Unspecified
OS:	Linux
Priority:	high
Severity:	high
Target Milestone:	---
Target Release:	4.8.z
Assignee:	Jiří Mencák
QA Contact:	Simon
Docs Contact:
URL:
Whiteboard:
Depends On:	1986477
Blocks:	1984730
TreeView+	depends on / blocked

Reported:	2021-07-28 16:33 UTC by OpenShift BugZilla Robot
Modified:	2021-08-16 18:32 UTC (History)
CC List:	3 users (show)
Fixed In Version:
Doc Type:	No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed:	2021-08-16 18:32:12 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Github	openshift cluster-node-tuning-operator pull 257	0	None	None	None	2021-08-04 01:00:40 UTC
Red Hat Product Errata	RHBA-2021:3121	0	None	None	None	2021-08-16 18:32:22 UTC

Comment 3 Simon 2021-08-12 18:03:06 UTC

$ oc get clusterversions.config.openshift.io 
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.8.0-0.nightly-2021-08-09-135211   True        False         25m     Cluster version is 4.8.0-0.nightly-2021-08-09-135211

$ oc get nodes
NAME                                         STATUS   ROLES           AGE   VERSION
ip-10-0-129-69.us-east-2.compute.internal    Ready    master,worker   49m   v1.21.1+9807387
ip-10-0-178-145.us-east-2.compute.internal   Ready    master,worker   50m   v1.21.1+9807387
ip-10-0-194-203.us-east-2.compute.internal   Ready    master,worker   49m   v1.21.1+9807387

$ oc project openshift-cluster-node-tuning-operator 
Now using project "openshift-cluster-node-tuning-operator" on server "https://api.skordas812b.qe.devcluster.openshift.com:6443".

$ oc get pods
NAME                                            READY   STATUS    RESTARTS   AGE
cluster-node-tuning-operator-55775db6c4-r79pl   1/1     Running   0          58m
tuned-gkkt4                                     1/1     Running   0          48m
tuned-vwskn                                     1/1     Running   0          48m
tuned-w5sqv                                     1/1     Running   0          48m

$ oc get pods -n openshift-apiserver
NAME                         READY   STATUS    RESTARTS   AGE
apiserver-866d54ffc8-4hgjr   2/2     Running   0          45m
apiserver-866d54ffc8-4xt6l   2/2     Running   0          43m
apiserver-866d54ffc8-8td2n   2/2     Running   0          40m

$ ap1=apiserver-866d54ffc8-4hgjr

$ ap2=apiserver-866d54ffc8-4xt6l

$ ap3=apiserver-866d54ffc8-8td2n

$ time oc delete pod $ap1 -n openshift-apiserver; time oc delete pod $ap2 -n openshift-apiserver; time oc delete pod $ap3 -n openshift-apiserver
pod "apiserver-866d54ffc8-4hgjr" deleted

real    1m12.749s
user    0m0.130s
sys     0m0.057s
pod "apiserver-866d54ffc8-4xt6l" deleted

real    1m17.044s
user    0m0.155s
sys     0m0.032s
pod "apiserver-866d54ffc8-8td2n" deleted

real    1m22.334s
user    0m0.188s
sys     0m0.041s

$ oc get pods
NAME                                            READY   STATUS    RESTARTS   AGE
cluster-node-tuning-operator-55775db6c4-r79pl   1/1     Running   0          66m
tuned-gkkt4                                     1/1     Running   0          57m
tuned-vwskn                                     1/1     Running   0          57m
tuned-w5sqv                                     1/1     Running   0          57m


$ oc get pods -n openshift-apiserver
NAME                         READY   STATUS    RESTARTS   AGE
apiserver-866d54ffc8-hmmn2   2/2     Running   0          7m23s
apiserver-866d54ffc8-hp5l5   2/2     Running   0          6m11s
apiserver-866d54ffc8-llttk   2/2     Running   0          3m3s

$ ap1=apiserver-866d54ffc8-hmmn2

$ ap2=apiserver-866d54ffc8-hp5l5

$ ap3=apiserver-866d54ffc8-llttk

$ time oc delete pods $ap1 $ap2 $ap3 -n openshift-apiserver
pod "apiserver-866d54ffc8-hmmn2" deleted
pod "apiserver-866d54ffc8-hp5l5" deleted
pod "apiserver-866d54ffc8-llttk" deleted

real    1m21.510s
user    0m0.180s
sys     0m0.041s

$ oc get pods
NAME                                            READY   STATUS    RESTARTS   AGE
cluster-node-tuning-operator-55775db6c4-r79pl   1/1     Running   0          71m
tuned-gkkt4                                     1/1     Running   0          61m
tuned-vwskn                                     1/1     Running   0          61m
tuned-w5sqv                                     1/1     Running   0          61m

Comment 5 errata-xmlrpc 2021-08-16 18:32:12 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 (OpenShift Container Platform 4.8.5 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/RHBA-2021:3121

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