-
Bug
-
Resolution: Done
-
Undefined
-
4.14
-
Important
-
Yes
-
False
-
-
-
8/22: discussion underway vis
OCPBUGS-16032(JC/YL)
Description of problem:
Upgrade recovery test fails when verifying the backup content after upgrade. Error snippet: " /var/recovery/usrlocal is not found."
Version-Release number of selected component (if applicable):
Upgrade 4.13.z to 4.14
How reproducible:
Every Time
Steps to Reproduce:
1. Hub cluster running OCP 4.13, TALM 4.14, ZTP 4.14 2. Spoke Cluster running 4.14 nightly build 3. Retrieve spoke cluster /var/recovery before upgrade. 4. Trigger platform-upgrade from OCP build 4.13.9 to 4.14 nightly build (ocp-far-edge-vran-upgrade-recovery pipeline can be used for this) 5. Verify Backup Completed. 6. Retrieve spoke cluster /var/recovery after upgrade. 7. Check and Verify the backup content after upgrade. 8. Observed required backup content doesn't exist. //System Logs Snippet// [~]$ oc get csv -n rhacm NAME DISPLAY VERSION REPLACES PHASE advanced-cluster-management.v2.8.1 Advanced Cluster Management for Kubernetes 2.8.1 advanced-cluster-management.v2.8.0 Succeeded openshift-gitops-operator.v1.9.1 Red Hat OpenShift GitOps 1.9.1 openshift-gitops-operator.v1.9.0 Succeeded topology-aware-lifecycle-manager.v4.14.0 Topology Aware Lifecycle Manager 4.14.0 Succeeded [~]$ oc version Client Version: 4.13.8 Kustomize Version: v4.5.7 Server Version: 4.13.8 Kubernetes Version: v1.26.6+73ac561 [ ~]$ [ ~]$ export KUBECONFIG='/home/kni/clusterconfigs/helix61/auth/kubeconfig' [~]$ [ ~]$ [ ~]$ oc version Client Version: 4.13.8 Kustomize Version: v4.5.7 Server Version: 4.14.0-0.nightly-2023-08-11-055332 Kubernetes Version: v1.27.4+deb2c60 [ ~]$ oc get clusterversions.config.openshift.io NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.14.0-0.nightly-2023-08-11-055332 True False 13h Cluster version is 4.14.0-0.nightly-2023-08-11-055332 [ ~]$
Actual results:
upgrade-recovery test fails when verifying the backup content after upgrade. " /var/recovery/usrlocal is not found." Actual backup content exits on spoke cluster host. $ ls -lrt total 36 drwxr-xr-x. 11 root root 114 Aug 21 00:59 local drwxr-xr-x. 99 root root 8192 Aug 21 01:35 etc drwxr-xr-x. 9 root root 4096 Aug 21 01:36 kubelet -rwx------. 1 root root 15881 Aug 21 02:22 upgrade-recovery.sh drwxr-xr-x. 2 root root 132 Aug 21 02:22 cluster -rw-r--r--. 1 root root 121 Aug 21 02:22 etc.exclude.list [recovery]# pwd /var/recovery [recovery]#
Expected results:
backup_content: - cluster - etc - usrlocal - kubelet - upgrade-recovery.sh
Additional info:
I could see directory called "local" on spoke cluster under /var/recovery . What is an expected behavior with 4.14 TALM in this case?