Trident reports offline volume as online

[bromaniac]

Describe the bug tridentctl reports state of backend volume as online when it isn't.

Environment Provide accurate information about the environment to help us reproduce the issue.

• Trident version: 23.01.1
• Trident installation flags used: default Helm install
• Container runtime: cri-o://1.24.5-2.rhaos4.11.gitb007cb6.el8
• Kubernetes version: v1.24.12+8f6c8a6
• Kubernetes orchestrator: OpenShift 4.11.35
• Kubernetes enabled feature gates:
• OS: Red Hat Enterprise Linux CoreOS 411.86.202304042133-0 (Ootpa)
• NetApp backend types: ONTAP 9.12.1P4
• Other:

To Reproduce Create an iscsi volume with Trident.

Somehow make the backend volume go offline with state space-error like this: https://kb.netapp.com/onprem/ontap/os/Lun_goes_offline_with_space-error

Do a tridentctl get volumes. The volume which is offline with space-error is reported as STATE online.

Expected behavior Preferably tridentctl should show STATE space-error but STATE offline would also be ok. STATE online however is wrong.

Additional context As an k8s/Trident operator I do not have access to NetApp. Only our storage team has that. When several of our PVC:s broke and I tried to investigate why, the volumes were reported as online. Looking in NetApp with the storage team, it turned out they were actully in state space-error because of snapshots not being delete as described in the link I posted above.

Best regards, Fredrik

[bromaniac]

I think this was fixed here https://github.com/NetApp/trident/issues/543