Uploaded image for project: 'OpenShift API for Data Protection'
  1. OpenShift API for Data Protection
  2. OADP-3710 Pod restore plugin has incorrect log message
  3. OADP-3757

[IBM QE-Z] Verify Bug OADP-3710 - Pod restore plugin has incorrect log message

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Undefined Undefined
    • OADP 1.3.1
    • None
    • None
    • None
    • False
    • Hide

      None

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

      Description of problem:

      I noticed a log message while I was running some restore operation on the cluster.  The log message suggest that it's backing up volumes instead it should be restoring the volumes that are backed up. Attached log message below. 

      time="2024-03-11T13:32:23Z" level=info msg="[pod-restore] checking if pod has volumes to back up" cmd=/plugins/velero-plugins logSource="/remote-source/src/github.com/konveyor/openshift-velero-plugin/velero-plugins/pod/restore.go:149" pluginName=velero-plugins restore=openshift-adp/test-restore 

      Link: https://github.com/openshift/openshift-velero-plugin/blob/master/velero-plugins/pod/restore.go#L149

      Slack discussion:- https://redhat-internal.slack.com/archives/C0144ECKUJ0/p1710164169038619

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

       

      How reproducible:
      Always 

       

      Steps to Reproduce:
      1. Deploy an application consisting PVC. 
      2. Run backup and restore

      Actual results:

      Velero pod has incorrect log message. 

       

      Expected results:

      Fix pod restore plugin log.

       

      Additional info:

              uprasad@redhat.com Ukthi Prasad
              akarol@redhat.com Aziza Karol
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: