I can consistently reproduce the connection closure ("connectionXXX:0: detected conn error (1020)") by invoking:
tgt-admin --update iqn.2010-10.org.openstack:volume-XXX -f
which is what happens at:
https://github.com/openstack/cinder/blob/master/cinder/volume/targets/iscsi.py#L338-L339
when an attached volume gets extended.
I've not yet been able to reproduce the "iscsiadm -m session" failure, though, even when continually running it in a loop whilst reproducing the connection closure as above... so I'm not sure if these two symptoms are actually connected.
I can consistently reproduce the connection closure ("connectionXXX:0: detected conn error (1020)") by invoking:
tgt-admin --update iqn.2010- 10.org. openstack: volume- XXX -f
which is what happens at:
https:/ /github. com/openstack/ cinder/ blob/master/ cinder/ volume/ targets/ iscsi.py# L338-L339
when an attached volume gets extended.
I've not yet been able to reproduce the "iscsiadm -m session" failure, though, even when continually running it in a loop whilst reproducing the connection closure as above... so I'm not sure if these two symptoms are actually connected.