If you use non RHEL OS, we need to restore existing LIO configuration by hand(or add this to boot script).
Cinder has a function to save LIO iSCSI configuration automatically to the /etc/targetcli/saveconfig.json by default.
We can use this.
So right recovery steps after c-vol node crash are;
(1) Reboot the server
(2) Restore /etc/targetcli/saveconfig.json
sudo targetctl restore /etc/targetcli/saveconfig.json
(3) Start c-vol service
And then, iSCSI connection from iscsi client will be recovered.
From my further investigation, this is not a bug but we need to know recovery steps for c-vol node crash with lioadm.
From the commit massage in https:/ /github. com/openstack/ cinder/ commit/ 706878deaaa5acb b8a577942a5a774 c58fe16332, saveconfig. json after rebooting the server. In this case, I guess LIO iSCSI configuration will be restored automatically.
I think RHEL has a "target.service" and this service restore /etc/targetcli/
If you use non RHEL OS, we need to restore existing LIO configuration by hand(or add this to boot script). saveconfig. json by default.
Cinder has a function to save LIO iSCSI configuration automatically to the /etc/targetcli/
We can use this.
So right recovery steps after c-vol node crash are; saveconfig. json saveconfig. json
(1) Reboot the server
(2) Restore /etc/targetcli/
sudo targetctl restore /etc/targetcli/
(3) Start c-vol service
And then, iSCSI connection from iscsi client will be recovered.