Description of problem: The filename displayed in the RecentBackup message is incorrect. The RecentBackup condition is telling "message": "UpgradeBackup pre 4.9 located at path /etc/kubernetes/cluster-backup/upgrade-backup-2021-09-15_100541 on node \"yangyang0915-2-88b9l-master-0.c.openshift-qe.internal\"", but the file does not exist. # oc debug node/yangyang0915-2-88b9l-master-0.c.openshift-qe.internal Starting pod/yangyang0915-2-88b9l-master-0copenshift-qeinternal-debug ... To use host binaries, run `chroot /host` Pod IP: 10.0.0.2 If you don't see a command prompt, try pressing enter. sh-4.4# chroot /host sh-4.4# ls /etc/kubernetes/cluster-backup/upgrade-backup-2021-09-15_100541 ls: cannot access '/etc/kubernetes/cluster-backup/upgrade-backup-2021-09-15_100541': No such file or directory sh-4.4# ls /etc/kubernetes/cluster-backup/ upgrade-backup-2021-09-15_100535 The exact file name is upgrade-backup-2021-09-15_100535 rather than upgrade-backup-2021-09-15_100541. Version-Release number of selected component (if applicable): How reproducible: 2/2 Steps to Reproduce: 1. Install a 4.8 cluster 2. Upgrade to 4.9 signed release 3. Check RecentBackup condition Actual results: The bakcup filename displayed in the RecentBackup condition does not exist Expected results: Display the exact backup filename in the condition message Additional info:
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 (Moderate: OpenShift Container Platform 4.10.3 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/RHSA-2022:0056