Created attachment 603070 [details] logs and screen shot Description of problem: I logged in to the device -> disconnected the device in vdsm using iscsiadm. reopen of the dialogue in UI shows the device connected even though its not connected in vds. so we are apparently reading logged in devices from the cache. even after I discovered domains again I still see the device logged in. Version-Release number of selected component (if applicable): si13.2 How reproducible: 100% Steps to Reproduce: 1. log in to several devices through the UI. 2. in the host use iscsiadm to disconnected on of the devices. 3. go back to the UI -> try to extend a domain -> device is still shown as connected 4. discover luns again -> device is still shown as connected 5. select lun and extend Actual results: we would fail extend since the device is no longer connected in the vds so it looks like we are reading from cache and not refreshing UI results. Expected results: we should refresh UI results. Additional info: device is Dafna-extend-02 [root@gold-vdsd ~]# iscsiadm -m session tcp: [14] 10.35.64.10:3260,1 Dafna-si13-01 tcp: [17] 10.35.64.10:3260,1 Dafna-si13-02 tcp: [18] 10.35.64.10:3260,1 Dafna-si13-03 tcp: [19] 10.35.64.10:3260,1 Dafna-extend-01
I logged in to 25-30 targets, after disconnecting the targets on the host, re-opening the dialog shows only the targets the with luns that the domain is attached to, closing.
I tested again in si20. it reproduced. reproduce: 1. create a domain. 2. go to host -> iscsiadm -m node -u 3. go to UI -> storage -> edit domain you can see that the lun appears as connected
Looks like it's fixed in SI21, please verify
it's not fixed in si21. This time it tool a long time for the edit domain dialogue to open and it showed an empty dialogue (probably because it did run discover on the host and found nothing) but, once I closed it it just kept appearing empty and the reply was too fast which suggests that we are not trying to discover again, and only after I moved between objects we sent the discover again.
Its not automatically triggering discovery, it only shows the attached devices, Did you get an empty dialog and you sure you had devices attached ?
(In reply to comment #5) > Its not automatically triggering discovery, it only shows the attached > devices, > Did you get an empty dialog and you sure you had devices attached ? yes
This is a total different behavior from the original cause of this bug, I couldn't reproduce the new behavior as well, closing.