Comment 8 for bug 1221525

Want to provide an update w/r/t this issue. I have tracked the problem down to the fact that HyperV has always been logging in to the iSCSI initiator again. It appears for LVM/iSCSI this isn't a problem. For storwize_svc, however, it appears to cause a COMM error to be produced.

I have a patch I am working on with Alex Pilotti and Lucian Petrut that handles the situation more intelligently, attempting to login, catching a failed login and then checking if we are already logged in. Hope to push up a patch with this fix soon.