Trident created NFS volume that can not work for the Grafana/Kafka
Applies to
- ONTAP 9
- NFS
- Trident
- Kubernetes (K8s)
Issue
- K8s cluster can create and bind the trident created volumes for Grafana / Kafka but the pod container crashes after a period of time and cannot start up normally.
- Grafana logs show
Starting DB migration
then no more further progress.
t=2021-02-26T03:27:49+0000 lvl=info msg="Connecting to DB" logger=sqlstore dbtype=sqlite3
t=2021-02-26T03:27:49+0000 lvl=info msg="Starting DB migration" logger=migrator
- The trident logs show the volume created normally.
time="2021-02-26T03:27:36Z" level=info msg="Found PVC for requested volume pvc-d49aec82-3971-4d37-9a1e-2e35b9ee356e." UID=d49aec82-3971-4d37-9a1e-2e35b9ee356e name=grafana-cluster-monitoring namespace=cattle-prometheus requestID=32f42bf8-7e2d-4e9e-805d-9bce67cee8d4 requestSource=CSI size="{{2147483648 0} {} 2Gi BinarySI}" storageClass=trident-ontap-nas
time="2021-02-26T03:27:36Z" level=info msg="Found storage class for requested volume pvc-d49aec82-3971-4d37-9a1e-2e35b9ee356e." name=trident-ontap-nas requestID=32f42bf8-7e2d-4e9e-805d-9bce67cee8d4 requestSource=CSI
- ONTAP ems logs show the volume created successfully.
[?] Fri Feb 26 11:02:30 HKT [netapp: wafl_exempt17: wafl.data.compaction.event:notice]: WAFL volume data compaction state changed in volume "trident_pvc_d49aec82_3971_4d37_9a1e_2e35b9ee356e" to "enabled".
[?] Fri Feb 26 11:02:30 HKT [netapp: wafl_spcd_main: monitor.volumes.one.ok:debug]: Volume trident_pvc_d49aec82_3971_4d37_9a1e_2e35b9ee356e@vserver:e725b4b5-22fe-11ea-a430-00a098ed83b2 is OK.