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

Taking a snapshot of byte-precision sized PVC fails

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • 0
    • None
    • None
    • None
    • None
    • OCPEDGE Sprint 269, OCPEDGE Sprint 270, OCPEDGE Sprint 274, OCPEDGE Sprint 275, OCPEDGE Sprint 276
    • 5
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This is an LVMS Bug Report:

      Please create & attach a must-gather as indicated by this Guide to collect LVMS relevant data from the Cluster (linked to the latest version, use older versions of the documentation for older OCP releases as applicable

      Please make sure that you describe your storage configuration in detail. List all devices that you plan to work with for LVMS as well as any relevant machine configuration data to make it easier for an engineer to help out.

      Description of problem:

      Taking a snapshot of a byte-precision sized PVC fails indefinitely

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

      4.17.4
      $ oc get csv -n openshift-storage | grep lvms
      lvms-operator.v4.17.4                     LVM Storage                                      4.17.4     lvms-operator.v4.17.3                     Succeeded 

      Steps to Reproduce:

      1. Create pvc, mount it so it binds
      $ cat podpvc.yaml 
      apiVersion: v1
      kind: PersistentVolumeClaim
      metadata:
        name: simple-pvc
      spec:
        volumeMode: Filesystem
        storageClassName: lvms-vg1
        accessModes:
          - ReadWriteOnce
        resources:
          requests:
            storage: 1136234735
      ---
      apiVersion: v1
      kind: Pod
      ...
        volumes:
        - name: mypvc
          persistentVolumeClaim:
            claimName: simple-pvc
      2. Snapshot said PVC
      $ cat snap.yaml 
      apiVersion: snapshot.storage.k8s.io/v1
      kind: VolumeSnapshot
      metadata:
        name: simple-snap
      spec:
        volumeSnapshotClassName: lvms-vg1
        source:
          persistentVolumeClaimName: simple-pvc

      Actual results:

      Fails with error:     message: 'Failed to check and update snapshot content: failed to take snapshot       of the volume 3c450d9c-d3fc-42c9-a004-e42a2874fa5e: "rpc error: code = OutOfRange       desc = requested size 1136238592 is smaller than source logical volume: 1136656384"'

      Expected results:

      Success, snapshot readytouse=true

      Additional info:

      Same happens with a CSI clone
      $ cat csiclone.yaml
      apiVersion: v1
      kind: PersistentVolumeClaim
      metadata:
          name: clone-of-simple-pvc
      spec:
        volumeMode: Filesystem
        accessModes:
        - ReadWriteOnce
        storageClassName: lvms-vg1
        resources:
          requests:
            storage: 1136234735
        dataSourceRef:
          kind: PersistentVolumeClaim
          name: simple-pvc
      
      Warning  ProvisioningFailed    3s (x4 over 13s)   topolvm.io_lvms-operator-8478bf6fbb-m6psg_e62a32ed-0552-46d0-aa95-4f860e995966  failed to provision volume with StorageClass "lvms-vg1": rpc error: code = OutOfRange desc = requested size 1136238592 is smaller than source logical volume: 1136656384

              bzamalut@redhat.com Bulat Zamalutdinov
              akalenyu Alex Kalenyuk
              None
              None
              Minal Pradeep Makwana Minal Pradeep Makwana
              None
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated: