PVC Mountpoint Not Legacy
Description
Problem/Justification
None
Impact
None
Activity
Show:
Jacob McDonald October 27, 2021 at 1:55 PM
So far I have not seen a recurrence of this issue. I have upgrades a dozen containers from 5 different apps, and everything seems fine. Ok to close those as not reproducible.
Waqar Ahmed October 22, 2021 at 3:57 AM
ping
Waqar Ahmed October 18, 2021 at 12:00 PM
can you confirm please if you are able to reproduce this ? I tried reproducing and was not able to do so
Cannot Reproduce
Pinned fields
Click on the next to a field label to start pinning.
Details
Details
Assignee
Triage TeamReporter
Jacob McDonaldLabels
Impact
High
Time remaining
0m
Components
Fix versions
Affects versions
Priority
LowKatalon Platform
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Katalon Platform
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Created October 14, 2021 at 6:20 PM
Updated July 6, 2022 at 9:02 PM
Resolved October 27, 2021 at 2:07 PM
I had installed the Syncthing app from TrueCharts, using the default PVC option for the app state.
After O(days) running successfully, I noticed the app state had been lost. During investigation, I was not able to start the container again after stopping it.
Further investigation revealed that the PVC dataset had been configured to use a mountpoint property other than legacy:
```
$ sudo zfs list | grep ix-applications/releases
...
vol1/ix-applications/releases/syncthing 2.73M 8.59T 153K /mnt/vol1/ix-applications/releases/syncthing
vol1/ix-applications/releases/syncthing/charts 498K 8.59T 396K /mnt/vol1/ix-applications/releases/syncthing/charts
vol1/ix-applications/releases/syncthing/volumes 2.00M 8.59T 153K /mnt/vol1/ix-applications/releases/syncthing/volumes
vol1/ix-applications/releases/syncthing/volumes/ix_volumes 243K 8.59T 153K /mnt/vol1/ix-applications/releases/syncthing/volumes/ix_volumes
vol1/ix-applications/releases/syncthing/volumes/pvc-a60047d2-a7fe-432a-ac5b-5bc8a3611145 1.53M 100G 1.39M /mnt/var/lib/kubelet/pods/9004eb8e-aa42-49b4-92fb-9709dd7b465a/volumes/kubernetes.io~csi/pvc-a60047d2-a7fe-432a-ac5b-5bc8a3611145/mount
...
```
Setting the mountpoint property to `legacy` fixed the issue with the container failing to start, and the app state was restored as expected.
Attached please find the debug in case this helps determine how/why the PVC mountpoint was set.