TridentProtect Backups Failing with Kopia Permission Denied
Applies to
- NetApp TridentProtect (Kubernetes/OpenShift)
- Kopia Data Mover Pods
- OpenShift clusters using SecurityContextConstraints (SCC)
- Environments using S3/Generic S3 as backup repository
Issue
- TridentProtect backup jobs fail during the Kopia data mover stage, despite successful completion of pre-backup webhooks, volume snapshots, and PVC clone operations. The following errors are observed in the Kopia pod logs:
Unable to createlogs directory: mkdir /app/logs: permission denied
ERROR errorconnecting to repository: repository not initialized in the provided storage
write error: unableto open log file: open /app/logs/cli-logs/...: no such file or directory
ERROR unable toconnect to repository: unable to write config file: unable to create configdirectory: mkdir /app/config: permission denied
ERROR openrepository: repository is not connected. See https://kopia.io/docs/repositories/
- TridentProtect controller logs show:
failed to get kopiasnapshot ID from pod logs: summary line with snapshot_id not found in Kopia logoutput
