[Openness 20.09.01] Deleted pods doesn't disappear and show NodeAffinity after master machine reboot

[haodengeke]

HW: SKL_VCACA
OS: CentOS 7.6.1810
Openness commit: 603268f
Flavor: media-analytics-vca

Restart the master machine after completing the deployment result:
kubectl get pods -A

NAMESPACE NAME READY STATUS RESTARTS AGE
default account-8d6c554f5-hl44j 1/1 Running 0 149m
default ad-content-5fd4684bf7-c2bqx 1/1 Running 0 149m
default ad-decision-7bf64d94c9-zc6zj 1/1 Running 0 149m
default ad-insertion-6b6fc765c9-5hjs5 1/1 Running 0 149m
default ad-transcode-568594c89-zmlcx 1/1 Running 0 149m
default analytics-5fbf9476fd-7n6x2 1/1 Running 0 149m
default cdn-6f9bf4d947-7gv94 1/1 Running 0 149m
default content-provider-569c44fb7c-7sxr5 1/1 Running 0 149m
default content-transcode-56b8658d57-hlgr7 1/1 Running 0 149m
default database-6b7f564b56-ch7t8 1/1 Running 0 149m
default intel-gpu-plugin-qrwsn 1/1 Running 0 168m
default intel-vpu-plugin-ptqtn 0/1 ContainerCreating 0 168m
default kafka-6f7f7b9d85-9xjgj 1/1 Running 3 149m
default kafka2db-6b58f9bdf9-rdgvr 1/1 Running 0 149m
default zookeeper-8f4b77cf7-cr6mz 1/1 Running 0 149m
kafka cluster-entity-operator-7cf56c9c5c-s7whf 3/3 Running 4 165m
kafka cluster-kafka-0 2/2 Running 2 166m
kafka cluster-zookeeper-0 1/1 Running 1 167m
kafka strimzi-cluster-operator-7d6cd6bdf7-xtm6j 1/1 Running 1 4h13m
kube-system coredns-66bff467f8-49mgr 1/1 Running 2 4h18m
kube-system coredns-66bff467f8-8rdr2 1/1 Running 2 4h18m
kube-system descheduler-cronjob-1607580960-cw77q 0/1 Completed 0 4m32s
kube-system descheduler-cronjob-1607581080-bbh5l 0/1 Completed 0 2m32s
kube-system descheduler-cronjob-1607581200-8k8qs 0/1 Completed 0 32s
kube-system etcd-av09-20-wp 1/1 Running 3 4h18m
kube-system kube-apiserver-av09-20-wp 1/1 Running 3 4h18m
kube-system kube-controller-manager-av09-20-wp 1/1 Running 2 4h18m
kube-system kube-proxy-6khsb 1/1 Running 2 4h18m
kube-system kube-proxy-b7xn8 1/1 Running 1 168m
kube-system kube-proxy-m7zbp 1/1 Running 0 168m
kube-system kube-scheduler-av09-20-wp 1/1 Running 4 4h9m
kube-system weave-net-dkbfq 2/2 Running 0 168m
kube-system weave-net-ksw9r 2/2 Running 4 168m
kube-system weave-net-n5lv7 2/2 Running 7 4h18m
openness docker-registry-deployment-54d5bb5c-4vxhw 0/1 NodeAffinity 0 4h18m
openness docker-registry-deployment-54d5bb5c-mdr62 1/1 Running 0 23m
openness eaa-5c87c49c9-b6wfj 1/1 Running 2 163m
openness edgedns-gsvqb 1/1 Running 1 163m
openness nfd-release-node-feature-discovery-master-78b5dc9595-s5w29 1/1 Running 2 4h7m
openness nfd-release-node-feature-discovery-worker-v4kjp 1/1 Running 3 168m
openness nfd-release-node-feature-discovery-worker-w2tgs 1/1 Running 4 168m
telemetry cadvisor-kvr84 2/2 Running 2 168m
telemetry cadvisor-r2j2q 2/2 Running 0 168m
telemetry collectd-7qbfv 2/2 Running 2 168m
telemetry collectd-bwzsj 2/2 Running 0 168m
telemetry custom-metrics-apiserver-54699b845f-lsbp5 0/1 NodeAffinity 0 4h9m
telemetry custom-metrics-apiserver-54699b845f-w42g8 1/1 Running 0 23m
telemetry grafana-6b79c984b-5wtk6 2/2 Running 0 23m
telemetry grafana-6b79c984b-z2l6q 0/2 NodeAffinity 0 4h5m
telemetry otel-collector-7d5b75bbdf-zf2dl 2/2 Running 2 4h10m
telemetry prometheus-node-exporter-dl77m 1/1 Running 3 168m
telemetry prometheus-node-exporter-kc59b 1/1 Running 2 168m
telemetry prometheus-server-776b5f44f-4qjzw 3/3 Running 0 23m
telemetry prometheus-server-776b5f44f-mwcz7 0/3 NodeAffinity 0 4h10m
telemetry telemetry-aware-scheduling-68467c4ccd-4nflp 2/2 Running 0 23m
telemetry telemetry-aware-scheduling-68467c4ccd-dn7c5 0/2 NodeAffinity 0 4h8m
telemetry telemetry-collector-certs-l5mdt 0/1 Completed 0 4h10m
telemetry telemetry-node-certs-psd77 1/1 Running 0 168m
telemetry telemetry-node-certs-qwwch 1/1 Running 1 168m

[tomaszwesolowski]

Hi,
We will look into the problem and get back to you but in the meantime we also recommend upgrading to version 20.12

[tomaszwesolowski]

Hi, could you share with us file Openness_experience_kit_archive.tar.gz that was created after deployment?

[haodengeke]

Same problem with openness 20.12.
Sorry, Openness_experience_kit_archive.tar.gz is automatically deleted after deployment.