Created attachment 607451 [details] vdsm logs Description of problem: When performing an operation on iscsi storage domains from the webadmin such as creating a domain, the dialog can stay open indefinitely. However, if, between the time login is selected for a target and the time "ok" is clicked the server disconnects from the storage (due to timeout/network error/manual disconnect) the webadmin is not aware of this and only sends createVG, which fails. Logs attached (vdsm) show time between connectStorageServer and createVG is about 17 minutes, and createVG fails (because storage was disconnected from host, may be due to timeout) Version-Release number of selected component (if applicable): rhevm-3.1.0-13.el6ev.noarch How reproducible: 100% Steps to Reproduce: 1. Open dialog click login 2. go to host and disconnect iscsi session 3. click ok in dialog Actual results: Expected results: Additional info:
Why is that a bug? 17 minutes is a lot of time. A web based dialogue may always have expired information/status. Take for example contention when you update a BZ, an expired sessions when a form is open too long on some sites, etc. In RHEV there may be many of those situations: * What happens if you get SPM re-election during this time? * What happens if one admin is editing a VM and another from a different session just deleted it? And so on and on. What is important is to have a proper failure message when the subsequent operation fails. So do you get a proper error? If so then please close as not a bug. If not then change the subject to fix the error message.
It's impossible and not interesting to handle all these situations. This can happen right after createVG command was sent and there is nothing to be done about it.
(In reply to comment #2) > It's impossible and not interesting to handle all these situations. > This can happen right after createVG command was sent and there is nothing > to be done about it. Are you referring to comment #1 or #0. As per comment #1, I fully agree the scenario is not a bug, however I still need to understand whether a proper error message was delivered.
(In reply to comment #3) > (In reply to comment #2) > > It's impossible and not interesting to handle all these situations. > > This can happen right after createVG command was sent and there is nothing > > to be done about it. > > Are you referring to comment #1 or #0. > As per comment #1, I fully agree the scenario is not a bug, however I still > need to understand whether a proper error message was delivered. If an improper error is thrown then a bug can be opened but nothing here would indicate that is the case.
(In reply to comment #5) > If an improper error is thrown then a bug can be opened but nothing here > would indicate that is the case. (In reply to comment #1) > What is important is to have a proper failure message when the subsequent > operation fails. > > So do you get a proper error? If so then please close as not a bug. If not > then change the subject to fix the error message. Gadi, the above question is for you