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

[4.15 EFS] Gid allocation values is not getting increased after assigning to 100 volumes

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Undefined Undefined
    • None
    • 4.15
    • Storage / Operators
    • None
    • No
    • False
    • Hide

      None

      Show
      None
    • Hide
      *Cause*: What actions or circumstances cause this bug to present.
      *Consequence*: What happens when the bug presents.
      *Fix*: What was done to fix the bug.
      *Result*: Bug doesn’t present anymore.
      Show
      *Cause*: What actions or circumstances cause this bug to present. *Consequence*: What happens when the bug presents. *Fix*: What was done to fix the bug. *Result*: Bug doesn’t present anymore.
    • Bug Fix
    • In Progress

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

      Description of problem:

      [4.15 EFS] Gid allocation values is not getting increased after assigning  to 100 volumes

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

      4.15.0-0.nightly-2023-12-04-223539 

      How reproducible:

      Always

      Steps to Reproduce:

          1. Install EFS cluster from flexy template aos-4_15/ipi-on-aws/versioned-installer-efs_operator-ci
          2. Create new sc with randome values ex: gidRangeStart: "20000" and gidRangeEnd: "50000"     
          3. Create pvc,dep and check the status. 
          4. Check the Access point status 

      Actual results:

      It is assigning different values in accesspoint  

      Expected results:

      1. It should assign as per the start values or ramdom values in between the range
      2. Gid values is not getting increased after 100 volumes. 

      Additional info:

      sc.yaml
      apiVersion: storage.k8s.io/v1
      kind: StorageClass
      metadata:
        name: mysc
      provisioner: efs.csi.aws.com
      reclaimPolicy: Delete
      volumeBindingMode: WaitForFirstConsumer
      parameters:
        basePath: "/basePath"
        directoryPerms: "777"
        fileSystemId: fs-068b18a45f696ada6
        gidRangeEnd: "50000"
        gidRangeStart: "20000"
        provisioningMode: efs-ap
        subPathPattern: /subPath/${.PVC.name}/foo
      allowVolumeExpansion: false
      
      
      rohitpatil@ropatil-mac Downloads % oc get pvc,pod -n testropatil 
      NAME  STATUS   VOLUME   CAPACITY   ACCESS MODES   STORAGECLASS   AGE
      persistentvolumeclaim/mypvc-fs    Bound    pvc-620a372b-997c-458d-b1b2-662cd38ac8a1   1Gi        RWX            mysc           20m
      persistentvolumeclaim/mypvc-fs2   Bound    pvc-b18800f2-b5e0-449c-9af7-31d5298de864   1Gi        RWX            mysc           9s
      
      
      NAME                             READY   STATUS    RESTARTS   AGE
      pod/mydep-fs-6c54858c74-h9bjk    1/1     Running   0          20m
      pod/mydep-fs2-6975b5f7b8-ms9sl   1/1     Running   0          9s 
      
      // Access points values 
      fsap-0ec144ba0ecb8e00a  /basePath/subPath/mypvc-fs/foo-0ae306dd-afd3-4bad-ba9d-41f689d4335d         49000 : 49000       49000 : 49000 (777)      Available
      fsap-0c30d562eeaeec2d4  /basePath/subPath/mypvc-fs2/foo-864485a0-ba97-4f8b-930e-031df80f2123    49001 : 49001   49001 : 49001 (777)      Available

            rbednar@redhat.com Roman Bednar
            openshift-crt-jira-prow OpenShift Prow Bot
            Rohit Patil Rohit Patil
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: