Closed swolfod closed 4 years ago
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen
.
Mark the issue as fresh with /remove-lifecycle rotten
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /close
@fejta-bot: Closing this issue.
I am trying to launch the pv deployment, but the persistent volume won't create and the log shows the following error:
provision "example/efs" class "aws-efs": failed to save persistentvolume "pvc-2227939f-596e-11ea-9c86-0270dd06cf60": PersistentVolume "pvc-2227939f-596e-11ea-9c86-0270dd06cf60" is invalid: spec.nfs.path: Invalid value: "EFS_AWS_DOMAIN:/efs-pvc-2227939f-596e-11ea-9c86-0270dd06cf60": must be an absolute path.
I searched around but didn't find anything relevant to this. Is this a new problem or did I miss anything?