Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Permission Error After Enabling Persistence in Parca StatefulSet #5368

Open
Chinnam08 opened this issue Dec 6, 2024 · 1 comment
Open

Permission Error After Enabling Persistence in Parca StatefulSet #5368

Chinnam08 opened this issue Dec 6, 2024 · 1 comment

Comments

@Chinnam08
Copy link

We have been using parca-dev/helm-charts for several months with the standard Deployment configuration, and everything has been working fine. Recently, we decided to enable persistence for the Parca server by adding the --enable-persistence flag. To achieve this, we replaced the Deployment with a StatefulSet and added a PersistentVolumeClaim. However, after making these changes, we started encountering a permission error.

volumeClaimTemplates:
- metadata:
     name: parca-storage
  spec:
     accessModes: [ "ReadWriteOnce" ]
     storageClassName: gp2-encrypted
      resources:
         requests:
         storage: 8Gi
           args:
              - /parca
              - --config-path=/var/parca/parca.yaml
              - --log-level=info
              - --cors-allowed-origins=*
              - --enable-persistence=true
             - --storage-path=/var/lib/parca
              - --storage-active-memory=2147483648

level=error name=parca ts=2024-11-14T04:58:34.983272541Z caller=main.go:66 msg="Program exited with error" err="Error Creating Dir: \"/data/metastore\" error: mkdir /data/metastore: permission denied"

It seems like Parca is unable to create the necessary directories due to permission issues, even though the StatefulSet and volume mounts appear to be configured correctly.

We followed the steps in issues like #3048, but we are still facing the permission issue.

We have tried adjusting the fsGroup, runAsUser, and runAsGroup in the securityContext, but it did not resolve the issue.

Could you please assist us in resolving this issue? Any guidance on how to fix the permissions would be greatly appreciated

@Chinnam08
Copy link
Author

We initially tried without specifying --storage-path=/var/lib/parca, which means we used the default path (/data). We only added /var/lib/parca in the attempts suggested in (#2089)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant