#Trident backends offline after AWS upgrades FSxN to 9.17.1P1

1 messages · Page 1 of 1 (latest)

dim arrow
#

AWS upgraded our FSxN instances to 9.17.1P1 and that appears to have broken Trident! Unable to deploy applications as the backend is offline on all of our k8s clusters using FSxN. Any suggestions on restoring Trident services? Support case 2010532457

time="2025-10-27T155029Z" level=error msg="GRPC error: rpc error: code = Internal desc = backend fsx-ontap-ue1-xxxx is not Online or Deleting" logLayer=csi_frontend requestID=7a23038f-2e9b-4443-9188-fed000b9b392 requestSource=CSI
time="2025-10-27T155029Z" level=error msg="Invalid backend state." expectedState=online/deleting logLayer=core requestID=2657a114-061b-4383-9feb-3f515e719bdf requestSource=CSI state=offline workflow="controller_server=unpublish"
time="2025-10-27T155029Z" level=error msg="Could not unpublish volume." error="backend fsx-ontap-ue1-xxxx is not Online or Deleting" logLayer=csi_frontend node=ip-10-185-197-99.ec2.internal requestID=2657a114-061b-4383-9feb-3f515e719bdf requestSource=CSI vol
ume=pvc-8433d14c-3f18-4539-b617-912e33fc89c8 workflow="controller_server=unpublish"
time="2025-10-27T155029Z" level=error msg="GRPC error: rpc error: code = Internal desc = backend fsx-ontap-ue1-xxxx is not Online or Deleting" logLayer=csi_frontend requestID=2657a114-061b-4383-9feb-3f515e719bdf requestSource=CSI

novel wolf
#

Noting 'ran update commands on 3 main clusters, which all now report backend state is 'online'. Changes to storage side do not automatically update Trident. A backend update refreshes/resyncs the controller and storage.