Ironic iscsi host fs goes into read-only after some network distruption

[Jacolex]

Hello
This is not a bug report, but question, how to avoid it. Sometimes baremetal instances deployed using cinder and iscsi are going into read-only file system, when something is wrong on the network.

# touch testfile
touch: cannot touch 'testfile': Read-only file system
# reboot
Failed to open initctl fifo: No such device or address

As above example, nothing is working on the host. So the question is: is there some solution to avoid such issues - configuration of iscsi target or something else, which will allow iscsi initiator to reconnect and bring the file system back to work?

[Radosław Piliszek (yoctozepto)]

Have you checked whether the relevant config is still present on the iSCSI target? I.e. does it allow this particular initiator like it did before? Also, who is the initiator? Is it the BIOS (UEFI)? Maybe the FC adapter needs a BIOS upgrade to fix an issue with reconnects?