The trident try to use CHAP authentication, but the target is created without the CHAP

[wycc]

After create the PV, the target is created correct at the NAS.

and the CHAP is off

However, we see lots of login fail

It looks like the trident try to connect to the NAS, but the target does not need it.

How can we change the trident to connect to ISCSI without authentication?

[davidcheng0716]

Hi @wycc,

CHAP authentication is not currently supported. It seems there is another issue.

First of all, please check that the iSCSI tool is properly installed on each node.

I need more information to identify the issue:

(1) Firmware version
(2) Error logs: When you deploy the Pods with PVC, check the logs through

  `kubectl logs -f trident-controller-xxxxxxxxxx-xxxxx -n trident -c trident-main`
  `kubectl logs -f trident-node-linux-xxxxx -n trident -c trident-main`

[wycc]

(1) QNAP NAS firmware version

(2) logs
log.zip

(3) YAMLs
yaml.zip

[wycc]

I found that the issue is in the network adaptor card. The device is mounted. However, it block when it is formmatted. We see lots of message in the demsg.

Therefore, we install in the other computers and it works well. Actually, the same server(Dell R740) does not work when we use NFS as well. This is why we try CSI driver. It looks like that this is an issue related to the network adaptor instead of CSI driver.

9586.993661] I/O error, dev sdd, sector 8702976 op 0x1:(WRITE) flags 0x0 phys_seg 128 prio class 0
[179598.764814] connection694:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4474267127, last ping 4474272256, now 4474277376
[179598.768607] connection694:0: detected conn error (1022)
[179610.539988] connection694:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4474278903, last ping 4474284032, now 4474289152
[179610.543789] connection694:0: detected conn error (1022)
[179622.315226] connection694:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4474290679, last ping 4474295808, now 4474300928
[179622.319025] connection694:0: detected conn error (1022)
[179634.090404] connection694:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4474302455, last ping 4474307584, now 4474312704
[179634.094207] connection694:0: detected conn error (1022)
[179634.094467] sd 16:0:0:1: [sdd] tag#35 FAILED Result: hostbyte=DID_TRANSPORT_DISRUPTED driverbyte=DRIVER_OK cmd_age=92s
[179634.094483] sd 16:0:0:1: [sdd] tag#35 CDB: Write(10) 2a 00 00 84 d8 00 00 04 00 00
[179634.094488] I/O error, dev sdd, sector 8706048 op 0x1:(WRITE) flags 0x4000 phys_seg 128 prio class 0
[179645.865609] connection694:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4474314230, last ping 4474319360, now 4474324480
[179645.869406] connection694:0: detected conn error (1022)
[179658.664734] connection694:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4474326988, last ping 4474332160, now 4474337280
[179658.668573] connection694:0: detected conn error (1022)
[179670.439923] connection694:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4474338807, last ping 4474343936, now 4474349056
[179670.443739] connection694:0: detected conn error (1022)
[179682.215128] connection694:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4474350583, last ping 4474355712, now 4474360832
[179682.218977] connection694:0: detected conn error (1022)