(In reply to Xiubo Li from comment #4)
...
> read
> /sys/class/iscsi_host/host415/device/session383/connection383:0/
> iscsi_connection/connection383:0/address: transport endpoint is not connected
> [...]
...
I do not have much experience with the kubernetes iscsi code. But it seems that the above error is not handled correctly at https://github.com/kubernetes/kubernetes/blob/master/pkg/volume/util/device_util_linux.go#L163
From my brief reading of the code, it should not return an error when reading the 'address' file (or others) fail, but instead continue with the loop and look at the next connection.
Humble, what do you think?