#Upgrades: Trident and ONTAP

1 messages · Page 1 of 1 (latest)

median wedge
#

https://github.com/NetApp/trident/issues/1001
https://github.com/NetApp/trident/issues/961

Both of these seem related. Wondering what the GenPop here thinnk and have actually observered.

A couple months, one of must customers expected a Non-Disruptive ONTAP upgrade from 9.13->9.14
ONTAP upgraded just fine. As soon as the second node rebooted, the trident-based nodes all barfed (Issue 961 above)

The issue was supposedly resolved in 24.10.1, but sadly, the customer was running 24.10.1 and it still happened.
The only real fix is after the upgrade, reboot the hosts (not restart services, reboot the hosts)

Now I see issue 1001. I have another customer getting ready to do just what it is (upgrade from 24.10.1 -> 25.02.1).
I worry that the customer will basically see the same issue (it looks like the same errors).

Have anyone out there actually updated 24.10.1 ->25.02.1 without issues?
What about updating ONTAP while using 24.10.1 and/or 25.02.1?

They are setup "correctly". ISCSI-A/iSCSI-B VLANs (not routed). Each host sees 4-paths to the storage.

GitHub

Describe the bug Recently we have performed trident upgrade to 25.02.1 (from 24.10.1) After upgrade was done by ‘operator’, and trident-node PODs were replaced – we faced tragic consequences – PODs...

GitHub

ISCSI Session healing will take the following: detect all ISCSI sessions that are not in "logged in" state wait for a timeout log them out and back in This has the impact of causing any e...