Created attachment 794305[details]
This is the engine.log file that shows the fails of the ISO storage.
Description of problem:
I have configured a data center to have an imported ISO domain with an IP address and path after the ISCSI storage was added. I then put the ISO domain in maintenance mode, detached the ISO and then deleted it.
At this time, the only storage that is showing, is the ISCSI storage.
I then try to add the same ISO storage with the same IP address and RHEV-M says it already exists and still no sign of it in the GUI. I *then* add the exact same ISO, but instead of using the IP address, I use the FQDN. This imports the ISO domain, correctly.
Version-Release number of selected component (if applicable):
RHEV-M 3.3 (is12)
How reproducible:
100%
Steps to Reproduce:
1. See above.
2.
3.
Actual results:
ISO storage fails to get added to RHEV-M
Expected results:
ISO storage succeeds to get added to RHEV-M
Additional info:
Ayal, you are referring to bug 991470.
It's similar, but not exactly identical - removing a domain from the GUI, with no errors, SHOULD also remove the connection record.
(In reply to Allon Mureinik from comment #2)
> Ayal, you are referring to bug 991470.
> It's similar, but not exactly identical - removing a domain from the GUI,
> with no errors, SHOULD also remove the connection record.
According to the logs, it seems like a duplicate of bug 1020812 which has been resolved for 3.3. The described scenario doesn't appear to reproduce any longer. Moving to ON_QA for re-verification (please note that 'Format Domain' option should be checked in order to completely remove the ISO domain).
Created attachment 794305 [details] This is the engine.log file that shows the fails of the ISO storage. Description of problem: I have configured a data center to have an imported ISO domain with an IP address and path after the ISCSI storage was added. I then put the ISO domain in maintenance mode, detached the ISO and then deleted it. At this time, the only storage that is showing, is the ISCSI storage. I then try to add the same ISO storage with the same IP address and RHEV-M says it already exists and still no sign of it in the GUI. I *then* add the exact same ISO, but instead of using the IP address, I use the FQDN. This imports the ISO domain, correctly. Version-Release number of selected component (if applicable): RHEV-M 3.3 (is12) How reproducible: 100% Steps to Reproduce: 1. See above. 2. 3. Actual results: ISO storage fails to get added to RHEV-M Expected results: ISO storage succeeds to get added to RHEV-M Additional info: