-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
4.14.0
-
Important
-
No
-
CNF RAN Sprint 245
-
1
-
False
-
This is a clone of issue OCPBUGS-22811. The following is the description of the original issue:
—
Description of problem:
While upgrading 3518 managed SNO clusters from 4.13.19 to 4.14.0 and precaching all clusters before the upgrade, all 3518 clusters failed to backup because of the cluster has no enough required disk sapce as shown bellow # oc --kubeconfig /root/hv-vm/kc/vm03080/kubeconfig get po -n openshift-talo-backup backup-agent-gtq5r NAME READY STATUS RESTARTS AGE backup-agent-gtq5r 0/1 Error 0 4h47m # oc --kubeconfig /root/hv-vm/kc/vm03080/kubeconfig logs -n openshift-talo-backup backup-agent-gtq5r INFO[0000] Successfully mounted /host/dev/shm INFO[0000] Successfully remounted /host/sysroot with r/w permission INFO[0000] Successfully renamed /run/ostree-booted to /run/ostree-booted.tmp INFO[0000] ------------------------------------------------------------ INFO[0000] Cleaning up old content... INFO[0000] ------------------------------------------------------------ INFO[0000] Old directories deleted with contents INFO[0000] Old contents have been cleaned up INFO[0025] Available disk space : 51.63 GiB; Estimated disk space required for backup: 56.74 GiB ERRO[0025] insufficient disk space to trigger backup INFO[0025] Successfully renamed /run/ostree-booted.tmp back to /run/ostree-booted
sakhoury@redhat.com helped to take a look at the environment and found that " it appears that the function that was created to do the estimation may be over-estimating the required amount"
Version-Release number of selected component (if applicable):
Versions ACM: 2.9.0-DOWNSTREAM-2023-10-26-18-39-52 Hub OCP: 4.13.19 Deployed OCP: 4.13.19, upgrade to 4.14.0 TALM - 4.14.0 (Threaded with 5 threads)
How reproducible:
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info:
- clones
-
-
- Closed
-
- is blocked by
-
-
- Closed
-
- links to
- mentioned on
