• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • None
    • master
    • None
    • Severity 3 - Minor

      Issue Summary

      Since NFS fixer pod has a pre-install hook annotation, Helm processes this template before it looks at others. This pod uses a PVC which Helm can create for you but it happens only after pre-install things are completed. It results in nfs fixer pod just sitting there in a pending state since it share-home PVC is never created.

      GitHub issue: https://github.com/atlassian-labs/data-center-helm-charts/issues/75

      Steps to Reproduce

      1. Deploy any DC product with Helm with

       

      {{ --set volumes.sharedHome.persistentVolumeClaim.create=true }}
      --set volumes.sharedHome.nfsPermissionFixer.enabled=true

      Expected Results

      NFS fixer pod does its job and the installation continues

      Actual Results

      NFS fixer pod stuck in a pending state because of a missing PVC:

      NAME                        READY   STATUS    RESTARTS   AGE
      bitbucket-nfs-fixer-jvx5n   0/1     Pending   0          4m51s
      postgres-postgresql-0       1/1     Running   0          14m
      
      Events:
        Type     Reason            Age    From               Message
        ----     ------            ----   ----               -------
        Warning  FailedScheduling  6m54s  default-scheduler  persistentvolumeclaim "bitbucket-shared-home" not found
        Warning  FailedScheduling  5m30s  default-scheduler  persistentvolumeclaim "bitbucket-shared-home" not found
      

      Workaround

      Removing pre-install hook annotation is a workaround but very unreliable since the pod can start after Jira/Connie/BBDC starts writing to share home.

            [SCALE-56] DC Helm Charts: NFS Fixer pod is stuck in pending state

            Bruno made changes -
            Remote Link Original: This issue links to "DCKUBE-131 (Bulldog)" [ 532262 ] New: This issue links to "DCKUBE-131 (JIRA Server (Bulldog))" [ 532262 ]
            Dylan Rathbone made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Needs Triage [ 10030 ] New: Closed [ 6 ]

            A fix for this issue has since been merged:

            https://github.com/atlassian-labs/data-center-helm-charts/pull/101

             Closing this out as resolved.

            Dylan Rathbone added a comment - A fix for this issue has since been merged: https://github.com/atlassian-labs/data-center-helm-charts/pull/101  Closing this out as resolved.
            Adam Brokes made changes -
            Remote Link New: This issue links to "DCKUBE-131 (Bulldog)" [ 532262 ]
            Adam Brokes made changes -
            Component/s New: Kubernetes [ 63401 ]
            Component/s Original: Docker [ 59292 ]
            Yevhen made changes -
            Description Original: h3. Issue Summary

            Since NFS fixer pod has a pre-install hook annotation, Helm processes this template before it looks at others. This pod uses a PVC which Helm can create for you but it happens only after pre-install things are completed. It results in nfs fixer pod just sitting there in a pending state since it share-home PVC is never created.
            h3. Steps to Reproduce
             # Deploy any DC product with Helm with

             

            {{ --set volumes.sharedHome.persistentVolumeClaim.create=true \}}
            {{--set volumes.sharedHome.nfsPermissionFixer.enabled=true}}
            h3. Expected Results

            NFS fixer pod does its job and the installation continues
            h3. Actual Results

            NFS fixer pod stuck in a pending state because of a missing PVC:
            {noformat}
            NAME READY STATUS RESTARTS AGE
            bitbucket-nfs-fixer-jvx5n 0/1 Pending 0 4m51s
            postgres-postgresql-0 1/1 Running 0 14m

            Events:
              Type Reason Age From Message
              ---- ------ ---- ---- -------
              Warning FailedScheduling 6m54s default-scheduler persistentvolumeclaim "bitbucket-shared-home" not found
              Warning FailedScheduling 5m30s default-scheduler persistentvolumeclaim "bitbucket-shared-home" not found
            {noformat}
            h3. Workaround

            Removing pre-install hook annotation is a workaround but very unreliable since the pod can start after Jira/Connie/BBDC starts writing to share home.
            New: h3. Issue Summary

            Since NFS fixer pod has a pre-install hook annotation, Helm processes this template before it looks at others. This pod uses a PVC which Helm can create for you but it happens only after pre-install things are completed. It results in nfs fixer pod just sitting there in a pending state since it share-home PVC is never created.

            GitHub issue: [https://github.com/atlassian-labs/data-center-helm-charts/issues/75]
            h3. Steps to Reproduce
             # Deploy any DC product with Helm with

             

            {\{ --set volumes.sharedHome.persistentVolumeClaim.create=true }}
             {{--set volumes.sharedHome.nfsPermissionFixer.enabled=true}}
            h3. Expected Results

            NFS fixer pod does its job and the installation continues
            h3. Actual Results

            NFS fixer pod stuck in a pending state because of a missing PVC:
            {noformat}
            NAME READY STATUS RESTARTS AGE
            bitbucket-nfs-fixer-jvx5n 0/1 Pending 0 4m51s
            postgres-postgresql-0 1/1 Running 0 14m

            Events:
              Type Reason Age From Message
              ---- ------ ---- ---- -------
              Warning FailedScheduling 6m54s default-scheduler persistentvolumeclaim "bitbucket-shared-home" not found
              Warning FailedScheduling 5m30s default-scheduler persistentvolumeclaim "bitbucket-shared-home" not found
            {noformat}
            h3. Workaround

            Removing pre-install hook annotation is a workaround but very unreliable since the pod can start after Jira/Connie/BBDC starts writing to share home.
            Yevhen created issue -

              Unassigned Unassigned
              c64f33b2bce3 Yevhen
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: