Comment 6 for bug 1221525

I think I understand what is happening here but am not sure what the best solution is at the moment.

The 'unexpected COM error' is because we are trying to log in to the portal when we are already logged in, I believe. If you go in on the windows GUI and make sure that the environment is all cleaned up, and if you have the patch for bug 1269915 applied, I am then able to successfully attach a volume. A second attempt to login on the same portal fails.

So, I tried doing the same test using an LVM share via iSCSI from a Linux box. It also was never seeing that the portal was already logged in. In that case, though, the second attempt, and all subsequent attempt to log in do not cause a COM error and the additional volumes mount fine.

Must be a different between tgtd and what the storwize uses where additional login attempts are concerned.

I need to investigate where the problem is here, but I think we may be getting close to a solution.