Uploaded image for project: 'OpenShift API for Data Protection'
  1. OpenShift API for Data Protection
  2. OADP-924

volsync-src-vsb pod going in error state

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Normal Normal
    • OADP 1.1.1
    • OADP 1.1.1
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • ToDo
    • 0
    • 0
    • Very Likely
    • 0
    • None
    • Unset
    • Unknown
    • No

      Description of problem: 

      Created a backup with MCG bucket, noticed that the volsync-src-vsb pod is going in error state. This pod is getting created continuously even after the Backup and VSB resource marked as failed.  

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

       

      How reproducible:
      Always (able to reproduce it with MCG bucket)

      Steps to Reproduce:
      1. Create a MCG bucket 
      2. Create a dpa, make sure the s3 url has prefix https
      3. Create a backup

      Actual results: 

      volsync-src-vsb pod is getting created continuously even after the Backup marked as failed.

      Expected results: 

      volsync-src-vsb pod should not get created after the backup marked as failed.

      Additional info:

      $ oc logs volsync-src-vsb-52c6b-rep-src-f2gz2
      Starting container
      VolSync restic container version: ACM-0.5.0-df22d29
      backup
      Testing mandatory env variables
      == Checking directory for content ===
      == Initialize Dir =======
      Fatal: create repository at s3:https://s3-openshift-storage.apps.oadp-21210.qe.gcp.devcluster.openshift.com/oadpbucket146538/openshift-adp/snapcontent-67805cac-c588-4e8e-b10e-11767698844b-pvc failed: client.BucketExists: Head "https://s3-openshift-storage.apps.oadp-21210.qe.gcp.devcluster.openshift.com/oadpbucket146538/": x509: certificate signed by unknown authority
      $ oc get pods
      NAME READY STATUS RESTARTS AGE
      openshift-adp-controller-manager-59947bf77d-cdt6g 1/1 Running 0 3h57m
      volsync-src-vsb-52c6b-rep-src-8tlz8 1/1 Running 0 15s
      volsync-src-vsb-52c6b-rep-src-f2gz2 0/1 Error 0 54s
      vsb-52c6b-pod 1/1 Running 0 35m
      $ oc get vsb 
      status:
      conditions:
      lastTransitionTime: "2022-10-14T12:15:16Z"
      message: cannot obtain source volumesnapshot oadp-812/velero-mysql-zk8kd
      reason: Error
      status: "False"
      type: Reconciled
      phase: PartiallyFailed
      
      
      $ oc get backup -o yaml
      status:
      completionTimestamp: "2022-10-14T12:12:56Z"
      csiVolumeSnapshotsAttempted: 1
      csiVolumeSnapshotsCompleted: 1
      errors: 1
      expiration: "2022-11-13T12:01:00Z"
      formatVersion: 1.1.0
      phase: PartiallyFailed
      progress:
      itemsBackedUp: 10
      totalItems: 10
      startTimestamp: "2022-10-14T12:01:00Z"
      version: 1 

              emcmulla@redhat.com Emily McMullan
              rhn-support-prajoshi Prasad Joshi
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: