nextcloud / nextcloud/helm

Nextcloud pods not coming up after enabling EFS as persistent volume.

Open
#232 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Persistence
Dominant language
Go Template
Stars
534
Forks
314
Avg merge
42m
Merged PRs (30d)
1

Description

Pods not coming up after enabling EFS as persistent volume.

Here are the application logs.

rsync: [receiver] chown "/var/www/html/apps/comments/l10n/.gl.js.3UZ34O" failed: Operation not permitted (1)
rsync: [receiver] chown "/var/www/html/apps/comments/l10n/.gl.json.eUCAHK" failed: Operation not permitted (1)
rsync: [generator] chown "/var/www/html/apps/encryption/appinfo" failed: Operation not permitted (1)
rsync: [generator] chown "/var/www/html/apps/encryption/composer" failed: Operation not permitted (1)
rsync: [generator] chown "/var/www/html/apps/encryption/composer/composer" failed: Operation not permitted (1)
rsync: [generator] chown "/var/www/html/apps/encryption/css" failed: Operation not permitted (1)
rsync: [generator] chown "/var/www/html/apps/encryption/img" failed: Operation not permitted (1)
rsync: [generator] chown "/var/www/html/apps/encryption/js" failed: Operation not permitted (1)
rsync: [generator] chown "/var/www/html/apps/encryption/l10n" failed: Operation not permitted (1)

here is PV manifest which is getting created after helm upgrade

apiVersion: v1
kind: PersistentVolume
metadata:
  annotations:
    pv.kubernetes.io/provisioned-by: efs.csi.aws.com
  creationTimestamp: "2022-05-06T08:05:29Z"
  finalizers:
  - kubernetes.io/pv-protection
  name: pvc-cb783745-2d5f-48cc-9c12-c9efca710bcd
  resourceVersion: "176218393"
  uid: bf1f0d91-67c1-477c-9d98-6610cc9cc41d
spec:
  accessModes:
  - ReadWriteOnce
  capacity:
    storage: 30Gi
  claimRef:
    apiVersion: v1
    kind: PersistentVolumeClaim
    name: nextcloud-nextcloud
    namespace: nextcloud
    resourceVersion: "176218388"
    uid: cb783745-2d5f-48cc-9c12-c9efca710bcd
  csi:
    driver: efs.csi.aws.com
    volumeAttributes:
      storage.kubernetes.io/csiProvisionerIdentity: 16XXXXXXXX3-8081-efs.csi.aws.com
    volumeHandle: fs-0XXXXXXXXX::fsap-XXXXXXXXXXX
  persistentVolumeReclaimPolicy: Delete
  storageClassName: efs-nextcloud
  volumeMode: Filesystem
status:
  phase: Bound

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the application logs and the generated PersistentVolume manifest, then inspect the Helm persistence settings for the EFS CSI volume. Reproduce the upgrade and verify that the Nextcloud pods become ready without rsync “Operation not permitted” errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, helm, kubernetes
Domain
cloud, devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.