iSCSI connections and storage put into maintenance

Hello, I have a cluster composed by two hosts connected to some iSCSI storage domains. I have put one host into maintenance and I see that all the iSCSI sessions are closed. So far so good. Then I put one storage domain into maintenance and I would expect to see on the active host the (2) iSCSI sessions versus this storage domain to get closed. Instead I continue to see them up and "multipath -l" command gives me the 2 paths for the LUN part of the storage domain connection. Is this expected and only when I execute detach of the SD I will get the closure of the iSCSI connections? Because the detach phase will unregister the VMs and I would like not to do it, but at the same time I will have a planned maintenance for this storage domain and I would like to clean the connections on host side, to let multipath happy when they will go down for some hours... Thanks in advance for any insight. Gianluca

Based on my Gluster setup,I have noticed that setting the storage domain into maintenance , just umounts the storage on all hosts.It also doesn't stop the gluster volume , so I do not expect the same for the iSCSI. I guess you can set it to maintenance and then manually logout the 2 hosts.Then , when you start it - it should login and mount the storage. Best Regards,Strahil Nikolov В петък, 20 декември 2019 г., 13:45:06 ч. Гринуич+2, Gianluca Cecchi <gianluca.cecchi@gmail.com> написа: Hello, I have a cluster composed by two hosts connected to some iSCSI storage domains.I have put one host into maintenance and I see that all the iSCSI sessions are closed. So far so good.Then I put one storage domain into maintenance and I would expect to see on the active host the (2) iSCSI sessions versus this storage domain to get closed.Instead I continue to see them up and "multipath -l" command gives me the 2 paths for the LUN part of the storage domain connection. Is this expected and only when I execute detach of the SD I will get the closure of the iSCSI connections? Because the detach phase will unregister the VMs and I would like not to do it, but at the same time I will have a planned maintenance for this storage domain and I would like to clean the connections on host side, to let multipath happy when they will go down for some hours... Thanks in advance for any insight. Gianluca _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/I7FQ3N7IAHQJLN...

On Fri, Dec 20, 2019 at 10:24 PM Strahil Nikolov <hunter86_bg@yahoo.com> wrote:
Based on my Gluster setup, I have noticed that setting the storage domain into maintenance , just umounts the storage on all hosts. It also doesn't stop the gluster volume , so I do not expect the same for the iSCSI.
Thanks for sharing this similar kind of behavior with Gluster.
I guess you can set it to maintenance and then manually logout the 2 hosts. Then , when you start it - it should login and mount the storage.
Yes, this was my idea too, but I wasn't sure about possible side effects during re-activation or normal workflow, so I asked if this is expected when you put a storage domain into maintenance. Gianluca
participants (2)
-
Gianluca Cecchi
-
Strahil Nikolov