[BUG]: Fix the perf issue related to fqdn resolution during export update with clients on isilon

[bpjain2004]

Bug Description

The driver always tries with the client fqdn first to update the export and it then tries with the client IP before failing. In some cases the Isilon is taking nearly 90sec before returning to the client with an error, if client fqdn is not resolvable. This is resulting in performance issues like timeout or delays in scheduling the pods.

Logs

Below 2 lines shows the time it has taken for the failure, which is adding to the delay.

time="2022-01-11T15:13:44Z" level=debug clusterName=isilon01 runid=18 msg="AddExportClientNetworkIdentifierByID client FQDN '[a172-24-89-176.deploy.akamaitechnologies.com](http://a172-24-89-176.deploy.akamaitechnologies.com/)' client IP '172.24.89.176'"
time="2022-01-11T15:15:18Z" level=warning clusterName=isilon01 runid=18 msg="failed to add client FQDN '[a172-24-89-176.deploy.akamaitechnologies.com](http://a172-24-89-176.deploy.akamaitechnologies.com/)' to export id '10' : 'failed to add client to export id '10' with access zone

Screenshots

No response

Additional Environment Information

No response

Steps to Reproduce

Driver installed with any Isilon which fails to resolve client fqdn

Expected Behavior

Driver should avoid tried with the failed client fqdn or ip for future calls.

CSM Driver(s)

CSI driver for powerscale 2.1.0

Installation Type

helm based

Container Storage Modules Enabled

No response

Container Orchestrator

Kubernetes 1.22

Operating System

RHEL 8.3