Comment 64 for bug 1569925

Please let me explain who I am and what we do to possibly shed some light on this.

I am an Interoperability engineer at NetApp. We test our storage products with many popular operating systems, adapters, protocols and switches, in varying combinations.

We test software initiator iscsi continuously (on other distros) with exactly the same configuration as I have described above and have never seen this behavior. Indeed whatever the problem is seems fixed in
Ubuntu upstream as I indicated above. This is also new behavior introduced between 14.04 and 16.04 because it did not occur in older versions.

The purpose of me asking to get this issue resolved is not to fix MY system, it is to fix it for my customers' systems. We will not post support for Ubuntu 16.04 (iscsi) without resolving this issue so that we don't put our customers in the same position.

With all that said, I do not currently have a configuration available or setup to reproduce this problem. If it is required, I can add it to the queue. When it is up and running, it reproduces every single time.

Other folks on the thread may actually have it up and running right now and be able to test the immediate fail before I get to it.