The Newly installed Trident operator can not identify the old PV/PVC with the old trident backend UUID
- Views:
- 689
- Visibility:
- Public
- Votes:
- 0
- Category:
- astra_trident
- Specialty:
- snapx
- Last Updated:
- 10/21/2021, 6:02:57 AM
Applies to
- Trident
- Kubernetes
Issue
- Deployed with tridentctl on Kubernetes.
- The Newly installed Trident operator can not identify the old PV/PVC with the old trident backend UUID.
- After upgraded tridentctl failed, then delete all the trident pods manually.
- Then installing the Trident operator, so the trident backend UUID is changed.
Example:
./tridentctl -n trident get backend
+-------------+----------------+--------------------------------------+--------+---------+
| NAME | STORAGE DRIVER | UUID | STATE | VOLUMES |
+-------------+----------------+--------------------------------------+--------+---------+
| nas-backend | ontap-nas | 98e19b74-aec7-4a3d-8dcf-128e5033b214 | online | 0 |
+-------------+----------------+--------------------------------------+--------+---------+
