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

Clean up debug output in csi-external-snapshotter used by kubevirt-csi

XMLWordPrintable

    • Low
    • None
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      Confusing debug message observed in logs when diagnosing issues with kubevirt-csi snapshotting:
      
      event.go:298] Event(v1.ObjectReference{Kind:"VolumeSnapshot", Namespace:"default", Name:"snap3", UID:"62016480-c1ae-4eb4-bfc3-f5eb79536a0a", APIVersion:"snapshot.storage.k8s.io/v1", ResourceVersion:"3023045", FieldPath:""}): type: 'Normal' reason: 'CreatingSnapshot' Waiting for a snapshot default/snap3 to be created by the CSI driver.
      snapshot_controller.go:965] Keeping PVC default/data-my-release-mariadb-0, it is used by snapshot default/snap3  
      snapshot_controller.go:1168] Raunak 1 %!s(*string=<nil>)
      snapshot_controller.go:1168] Raunak 1 %!s(*string=<nil>)
      
      This correlates to the following code in the github repo:
      
      https://github.com/openshift/csi-external-snapshotter/blob/4f2955c7c90cd150f9dfae782148d0fa8eba7342/pkg/common-controller/snapshot_controller.go#L1167C21-L1168C2

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

          Observed in 4.16, but code has been in the repo for over a year    

      Actual results:

         Spurious debug messages observed which confused customer 

      Expected results:

          Suppress or remove debug logging code that does not serve a purpose in released versions

      Additional info:

          

              rh-ee-mpatlaso Maxim Patlasov
              rhn-support-pauwebst Paul Webster
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: