PowerFlex: SDNAS file cluster registration failed

SDNAS GW connects to the block gateway to get all the storage pool details to validate if the request provided by ASM is proper).
This token gets generated only at the time of the SDNAS GW start sequence. In this system where registration failed, the Bearer token is null due to some authentication issue in SSO. Post that sequence, SSO has recovered but SDNAS GW has already started

thin-deployer-6d8dffddff-768p8:/opt/Dell/ASM/deployments/8aaa773f83c8a8810183d905cce855f4 # cat sdnasgw_exception.log
#<ASM::UserException: PowerFlex File cluster registration fail for M&O Gateway: {"messages"=>[{"code"=>"0xE08010230001", "severity"=>"Error", "message_l10n"=>"Error while registering the Cluster.", "arguments"=>["{\n  \"message\" : \"Error\",\n  \"httpStatusCode\" : 500,\n  \"errorCode\" : 0\n}"]}]}.>

/opt/asm-deployer/lib/asm/provider/elementmanager/sdnas.rb:1089:in `register_sdnas_cluster'
/opt/asm-deployer/lib/asm/provider/elementmanager/sdnas.rb:315:in `configure_sdnas_cluster'
/opt/asm-deployer/lib/asm/service_deployment.rb:4080:in `process_sdnas'
/opt/asm-deployer/lib/asm/service_deployment.rb:1493:in `block in create_component_thread't

This happens only if at the startup of SDNAS GW pod is not started /initiated properly. To the end customer PowerFlex File Cluster Registration Fails for SDNAS GW with an error "Error while registering the Cluster." "httpStatusCode": 500.

Make sure that SSO pod is up and running by running following command on one of the MVMs

kubectl get pods -A -o wide | grep sso

 Then restart the SDNAS GW pod and then retry registration.

kubectl get pods -n powerflex | grep -i sdnasgw | awk {'print $1'} | xargs kubectl delete pods -n powerflex