-
Bug
-
Resolution: Done-Errata
-
Critical
-
4.14.0, 4.15.0
-
No
-
Proposed
-
False
-
-
This is a clone of issue OCPBUGS-18990. The following is the description of the original issue:
—
Description of problem:
The script refactoring from https://github.com/openshift/cluster-etcd-operator/pull/1057 introduced a regression. Since the static pod list variable was renamed, it is now empty and won't restore the non-etcd pod yamls anymore.
Version-Release number of selected component (if applicable):
4.14 and later
How reproducible:
always
Steps to Reproduce:
1. create a cluster 2. restore using cluster-restore.sh
Actual results:
the apiserver and other static pods are not immediately restored The script only outputs this log: removing previous backup /var/lib/etcd-backup/member Moving etcd data-dir /var/lib/etcd/member to /var/lib/etcd-backup starting restore-etcd static pod
Expected results:
the non-etcd static pods should be immediately restored by moving them into the manifest directory again. You can see this by the log output: Moving etcd data-dir /var/lib/etcd/member to /var/lib/etcd-backup starting restore-etcd static pod starting kube-apiserver-pod.yaml static-pod-resources/kube-apiserver-pod-7/kube-apiserver-pod.yaml starting kube-controller-manager-pod.yaml static-pod-resources/kube-controller-manager-pod-7/kube-controller-manager-pod.yaml starting kube-scheduler-pod.yaml static-pod-resources/kube-scheduler-pod-8/kube-scheduler-pod.yaml
Additional info:
- clones
-
OCPBUGS-18990 cluster-restore.sh does not move static pods back
- Closed
- is blocked by
-
OCPBUGS-18990 cluster-restore.sh does not move static pods back
- Closed
- links to
-
RHSA-2023:5006 OpenShift Container Platform 4.14.z security update