Cosmetic error seen after Trident upgrade to 25.02.1
- Views:
- 14
- Visibility:
- Public
- Votes:
- 0
- Category:
- trident-kubernetes
- Specialty:
- snapx
- Last Updated:
- 5/30/2025, 6:49:16 AM
Applies to
- Trident 25.02.1
- Trident upgrade
Issue
- Cosmetic error seen after successful Trident upgrade to 25.02.1
ERRO Trident REST interface was not available after 180.00 seconds.
FATA Install failed; unable to upgrade connection: unable to upgrade: unable to negotiate protocol: client supports [v5.channel.k8s.io], server accepts [v4.channel.k8s.io v3.channel.k8s.io v2.channel.k8s.io channel.k8s.io]
unable to upgrade: unable to negotiate protocol: client supports [v5.channel.k8s.io], server accepts [v4.channel.k8s.io v3.channel.k8s.io v2.channel.k8s.io channel.k8s.io]; unable to upgrade connection: unable to upgrade: unable to negotiate protocol: client supports [v5.channel.k8s.io], server accepts [v4.channel.k8s.io v3.channel.k8s.io v2.channel.k8s.io channel.k8s.io]
unable to upgrade: unable to negotiate protocol: client supports [v5.channel.k8s.io], server accepts [v4.channel.k8s.io v3.channel.k8s.io v2.channel.k8s.io channel.k8s.io]; use 'tridentctl logs' to learn more. Resolve the issue; use 'tridentctl uninstall' to clean up; and try again.
- Trident functions work as expected and PVCs can be created and deleted