[BUG]: PowerStore CSI appears to look for iSCSI when FC only is being used

[DougBernhardt]

Bug Description

attach-controller can't attach volume: AttachVolume.Attach failed for volume "csivol-61a1cb94f1" : rpc error: code = Internal desc = could not get iscsiTargets: can't get iscsi target address

This is on an FC system. iSCSI is not configured. FC only should not be a problem.

I even tried adding the following to a new storage class: AllowedTopologies: Term 0: csi-powerstore.dellemc.com/xx.xx.xx.xx-fc in [true]

Logs

AttachVolume.Attach failed for volume "csivol-61a1cb94f1" : rpc error: code = Internal desc = could not get iscsiTargets: can't get iscsi target address

Screenshots

No response

Additional Environment Information

No response

Steps to Reproduce

create deployment that uses pvc.

Expected Behavior

volume should attach fine

CSM Driver(s)

CSI Driver for PowerStore v2.2.0

Installation Type

No response

Container Storage Modules Enabled

No response

Container Orchestrator

Kubernetes v1.23.5

Operating System

RHEL 8.5

[shanmydell]

@francis-nijay : Could you please have a look?

[francis-nijay]

Hi @DougBernhardt ,

Can you please let us know the value of blockProtocol from the secret created for csi-powerstore. If iSCSI is mentioned, then the driver will look for iSCSI initiators.

[DougBernhardt]

blockProtocol: "FC"

From: Francis Nijay @.***> Sent: Thursday, April 7, 2022 4:41 AM To: dell/csm Cc: Bernhardt, Doug; Mention Subject: Re: [dell/csm] [BUG]: PowerStore CSI appears to look for iSCSI when FC only is being used (Issue #252)

[EXTERNAL EMAIL]

Hi @DougBernhardt [github.com]https://urldefense.com/v3/__https:/github.com/DougBernhardt__;!!LpKI!0wjRZlxqnz-JSL4qZSit4RgYQD3Z5lwevxrddkvZMBq3XpZEiKAEVN-liMxve2GSreg$ ,

Can you please let us know the value of blockProtocol from the secret created for csi-powerstore. If iSCSI is mentioned, then the driver will look for iSCSI initiators.

- Reply to this email directly, view it on GitHub [github.com]https://urldefense.com/v3/__https:/github.com/dell/csm/issues/252*issuecomment-1091436486__;Iw!!LpKI!0wjRZlxqnz-JSL4qZSit4RgYQD3Z5lwevxrddkvZMBq3XpZEiKAEVN-liMxv8vSPssI$, or unsubscribe [github.com]https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AJNSSEQ755DQBME3XE3ULPDVD2UUPANCNFSM5SXHKMJA__;!!LpKI!0wjRZlxqnz-JSL4qZSit4RgYQD3Z5lwevxrddkvZMBq3XpZEiKAEVN-liMxv7o3ByzY$. You are receiving this because you were mentioned.Message ID: @.***>

Internal Use - Confidential

[DougBernhardt]

Regardless of the blockProtocol value, it appears to be checking to see if iSCSI has been enabled on the array. Once I enabled it on the array, then it works. This is a workaround, but a FC only array should not be required to have iSCSI configured.

From: Francis Nijay @.***> Sent: Thursday, April 7, 2022 4:41 AM To: dell/csm Cc: Bernhardt, Doug; Mention Subject: Re: [dell/csm] [BUG]: PowerStore CSI appears to look for iSCSI when FC only is being used (Issue #252)

[EXTERNAL EMAIL]

Hi @DougBernhardt [github.com]https://urldefense.com/v3/__https:/github.com/DougBernhardt__;!!LpKI!0wjRZlxqnz-JSL4qZSit4RgYQD3Z5lwevxrddkvZMBq3XpZEiKAEVN-liMxve2GSreg$ ,

Can you please let us know the value of blockProtocol from the secret created for csi-powerstore. If iSCSI is mentioned, then the driver will look for iSCSI initiators.

- Reply to this email directly, view it on GitHub [github.com]https://urldefense.com/v3/__https:/github.com/dell/csm/issues/252*issuecomment-1091436486__;Iw!!LpKI!0wjRZlxqnz-JSL4qZSit4RgYQD3Z5lwevxrddkvZMBq3XpZEiKAEVN-liMxv8vSPssI$, or unsubscribe [github.com]https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AJNSSEQ755DQBME3XE3ULPDVD2UUPANCNFSM5SXHKMJA__;!!LpKI!0wjRZlxqnz-JSL4qZSit4RgYQD3Z5lwevxrddkvZMBq3XpZEiKAEVN-liMxv7o3ByzY$. You are receiving this because you were mentioned.Message ID: @.***>

Internal Use - Confidential

[francis-nijay]

@DougBernhardt Can you please share controller and node logs to find where the check happens and make a fix if necessary.

[Daniel-Vaz]

I currently am encountering this same issue.

Kubernetes Version: v1.22.8
Kubernetes Distribution: Anthos on BareMetal 1.11.0
PowerStore CSI Driver version: 2.2.0
Installation Type: Helm
Nodes OS: Oracle Linux 8.4

I configured the secret and helm values to deploy de driver using FiberChannel for the connection (please look into the attached files to see the configurations that were used - values.zip). Then installed the Powerstore CSI driver using Helm, and everything was deployed successfully, and running the verify.sh script reports no errors.

We then proceeded to create a XFS Storage Class:

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: powerstore-xfs
parameters:
  FsType: xfs
provisioner: csi-powerstore.dellemc.com
allowVolumeExpansion: false
reclaimPolicy: Delete
volumeBindingMode: WaitForFirstConsumer

And a PVC:

kind: PersistentVolumeClaim
apiVersion: v1
metadata:
  name: pvol1
spec:
  accessModes:
  - ReadWriteOnce
  volumeMode: Filesystem
  resources:
    requests:
      storage: 100Mi
  storageClassName: powerstore-xfs

When we then create a Pod that mounts the previously mentioned PVC locally, we see that a PV gets created and Bound to the PVC correctly but the Pods gets stuck in a ContainerCreating phase with the following logs when described:

Warning FailedAttachVolume 40s (x9 over 2m52s)  attachdetach-controller AttachVolume.Attach failed for volume "csivol-ee3218d5c6" : rpc error: code = Internal desc = could not get iscsiTargets: can't get iscsi target address

We configured everything to use FC, but the Pod is insisting on using ISCi.

[francis-nijay]

@Daniel-Vaz The settings seem to be right. Can you please share controller and node driver logs?

[Daniel-Vaz]

@francis-nijay Here you go: logs.zip

[harishp8889]

@DougBernhardt This is fixed and available in the nightly build

[Prabhu-Dell]

Issue fixed.