Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-22223

TALM Backup Fails with Error: no such file or directory

XMLWordPrintable

    • No
    • False
    • Hide

      None

      Show
      None

      This is a clone of issue OCPBUGS-21749. The following is the description of the original issue:

      Description of problem:

      TALM backup consistently fails with Error: no such file or directory 

      Version-Release number of selected component (if applicable):

      TALM bundle 4.14.0-82

      How reproducible:

      Always

      Steps to Reproduce:

      1.Create and enable CGU with backup: true.
      2. CGU fails with UnrecoverableError
      3. TALM backup pod shows 
         INFO[0000] Error: no such file or directory                 
         ERRO[0000] exit status 1                                
      

      Actual results:

      $ oc logs -n openshift-talo-backup backup-agent-5z9s5 --follow
      INFO[0000] Successfully remounted /host/sysroot with r/w permission 
      INFO[0000] ------------------------------------------------------------ 
      INFO[0000] Cleaning up old content...                   
      INFO[0000] ------------------------------------------------------------ 
      INFO[0000] 
      fullpath: /var/recovery/cluster             
      INFO[0000] 
      fullpath: /var/recovery/upgrade-recovery.sh 
      INFO[0000] Old directories deleted with contents        
      INFO[0000] Old contents have been cleaned up            
      INFO[0000] Available disk space : 299.73 GiB; Estimated disk space required for backup: 3.03 GiB  
      INFO[0000] Sufficient disk space found to trigger backup 
      INFO[0000] Upgrade recovery script written              
      INFO[0000] Running: bash -c /var/recovery/upgrade-recovery.sh --take-backup --dir /var/recovery 
      INFO[0000] ##### Mon Oct 16 14:51:10 UTC 2023: Taking backup 
      INFO[0000] ##### Mon Oct 16 14:51:10 UTC 2023: Wiping previous deployments and pinning active 
      INFO[0000] error: Out of range deployment index 1, expected < 1 
      INFO[0000] Deployment 0 is already pinned               
      INFO[0000] ##### Mon Oct 16 14:51:10 UTC 2023: Backing up container cluster and required files 
      INFO[0000] Certificate /etc/kubernetes/static-pod-certs/configmaps/etcd-serving-ca/ca-bundle.crt is missing. Checking in different directory 
      INFO[0000] Certificate /etc/kubernetes/static-pod-resources/etcd-certs/configmaps/etcd-serving-ca/ca-bundle.crt found! 
      INFO[0000] found latest kube-apiserver: /etc/kubernetes/static-pod-resources/kube-apiserver-pod-5 
      INFO[0000] found latest kube-controller-manager: /etc/kubernetes/static-pod-resources/kube-controller-manager-pod-9 
      INFO[0000] found latest kube-scheduler: /etc/kubernetes/static-pod-resources/kube-scheduler-pod-7 
      INFO[0000] found latest etcd: /etc/kubernetes/static-pod-resources/etcd-pod-3 
      INFO[0000] Error: no such file or directory             
      INFO[0000] Error: no such file or directory             
      INFO[0000] mkdir: cannot create directory '/etc/kubernetes/static-pod-resources/bin': Read-only file system 
      INFO[0000] ##### Mon Oct 16 14:51:10 UTC 2023: Cluster backup failed 
      ERRO[0000] exit status 1

      Expected results:

      Backup is successful

      Additional info:

       

            jche@redhat.com Jun Chen
            openshift-crt-jira-prow OpenShift Prow Bot
            Joshua Clark Joshua Clark
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: