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

[4.15 EFS Rebase] Gid allocation values should assign accesspoint values from gidRangeStart instead of gidRangeEnd values

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Minor Minor
    • None
    • premerge, 4.15
    • Storage / Operators
    • None
    • Low
    • No
    • False
    • Hide

      None

      Show
      None
    • N/A
    • Release Note Not Required

      Description of problem:

      Gid allocation values should assign in ascending order for access points instead of in descending order

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

      4.15.0-0.nightly-2023-11-04-120954

      How reproducible:

      Always

      Steps to Reproduce:

      1. Create AWS EFS cluster from flexy template. 
         Flexy template: aos-4_15/ipi-on-aws/versioned-installer-efs_operator-ci 
      2. Check the efs operator, driver, sc is installed successfully
      3. Edit the csv values for parameters DRIVER_IMAGE and relatedImages(ose-aws-efs-csi-driver-container-rhel8) with sha value that pushed in quay.io site
      
      oc get csv -n openshift-cluster-csi-drivers
       
      oc edit csv aws-efs-csi-driver-operator.v4.15.0-202311031046 -n openshift-cluster-csi-drivers
        - name: DRIVER_IMAGE
          value: quay.io/rhn_support_ropatil/aws-efs-csi-driver@sha256:xxxx
        relatedImages:
        - image: quay.io/rhn_support_ropatil/aws-efs-csi-driver@sha256:xxxx
          name: ose-aws-efs-csi-driver-container-rhel8
      4. Create new sc, pvc, pod and check for access point in aws web console
      
      Discussion: https://redhat-internal.slack.com/archives/GK0DA0JR5/p1699011876797939 

      Actual results:

      It is assigning values in ascending order

      Expected results:

      It should assign the values in ascending order instead of descending order

      Additional info:

      sc_pvc_dep.yaml
      apiVersion: storage.k8s.io/v1
      kind: StorageClass
      metadata:
        name: efs-sc1
      parameters:
        basePath: "/dynamic_provisioning"
        directoryPerms: "777"
        fileSystemId: fs-xxxx
        gidRangeEnd: "2000"
        gidRangeStart: "1000"
        provisioningMode: efs-ap
      provisioner: efs.csi.aws.com
      reclaimPolicy: Delete
      volumeBindingMode: Immediate
      ---
      apiVersion: v1
      kind: PersistentVolumeClaim
      metadata:
        name: mypvc-fs
        namespace: testropatil
      spec:
        accessModes:
          - ReadWriteOnce
        volumeMode: Filesystem
        storageClassName: efs-sc1
        resources:
          requests:
            storage: 1Gi
      ---
      apiVersion: apps/v1
      kind: Deployment
      metadata:
        name: mydep-fs
        namespace: testropatil
      spec:
        replicas: 1
        selector:
          matchLabels:
            app: hello-storage1
        template:
          metadata:
            labels:
              app: hello-storage1
          spec:
            containers:
            - name: hello-storage
              image: quay.io/openshifttest/hello-openshift@sha256:b1aabe8c8272f750ce757b6c4263a2712796297511e0c6df79144ee188933623
              ports:
              - containerPort: 80
              volumeMounts:
              - name: local
                mountPath: /mnt/storage
            volumes:
            - name: local
              persistentVolumeClaim:
                claimName: mypvc-fs

              rbednar@redhat.com Roman Bednar
              ropatil@redhat.com Rohit Patil
              Rohit Patil Rohit Patil
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: