NetApp
Trident issue: failed to unstage volume
Describe the bug A clear and concise description of what the bug is.
Environment Provide accurate information about the environment to help us reproduce the issue.
- Trident version: REVISION UPDATED STATUS CHART APP VERSION DESCRIPTION 20 Fri Mar 15 08:50:14 2024 superseded trident-operator-100.2402.0 24.02.0 Upgrade complete 21 Fri Mar 15 08:50:16 2024 deployed trident-operator-100.2402.0 24.02.0 Upgrade complete
- Trident installation flags used: Trident is installed with helm via fleet
- Container runtime: [e.g. Docker 19.03.1-CE] flatcar 3602.2.3
- Kubernetes version: [e.g. 1.15.1] 1.27
- Kubernetes orchestrator: [e.g. OpenShift v3.11, Rancher v2.3.3] Rancher v2.8.2
- Kubernetes enabled feature gates: [e.g. CSINodeInfo] ???
- OS: [e.g. RHEL 7.6, Ubuntu 16.04] flatcar 3602.2.3
- NetApp backend types: [e.g. CVS for AWS, ONTAP AFF 9.5, HCI 1.7] NetApp Version 9.10.1P7
- Other:
To Reproduce Steps to reproduce the behavior: We receive the errors in the trident pods. Expected behavior A clear and concise description of what you expected to happen.
We expect the pods to be clean from errors.
Additional context Add any other context about the problem here.
@machrrab Can you please elaborate more on the actual problem along with debug logs that would help us isolate the issue.
- steps to reproduce.
- upgrade path that is carried out. Looked at the logs posted here (debug is not enabled and hence missing more information on the issue).
Hi Ravi, With the command I get all logs with trident-main container: k -n trident-csi get pods| grep -v NAME|awk '{print $1}'|xargs -I {} kubectl -n trident-csi logs {} trident-main
So, if there is another way to get debug logs please let know.
Hi @machrrab , You may please refer https://docs.netapp.com/us-en/trident/troubleshooting.html#general-troubleshooting to enable debug. And then collect the logs, which would help us more to understand the issue.
