Hide Forgot
Description of problem: Import of a data domain is available for data centers from version 3.5 and above, in case we select a 3.5 data center and then select a lower version data center, the import of a data domain options are not cleared and are selectable Version-Release number of selected component (if applicable): 3.5 How reproducible: 100% Steps to Reproduce: 1. In the storage domain main tab click on "Import domain" 2. If the default domain selected is of version <3.5 select "None" and then return to the default domain 3. If the default domain select is 3.5 select a version <3.5 domain Actual results: When the domain with a version lower than 3.5 is selected the import data domain options will not disappear and remain selectable even though the action is not supported Expected results: The options should not be selectable for domain lower than version 3.5 Additional info:
Does it at least fail with a CDA in the backend?
We should be able to import a Storage Domain for Data Center lower then 3.5, but if this storage domain is already attached to another Data Center, then we will fail. So I think that the appropriate solution for this bug is to let the user import a Storage Domain for Data Center lower the 3.5 version, if the Storage Domain is already attached to another Data Center we should block this in the CDA other wise it should let the Storage Domain to be attached to the Data Center and add a warning whether this Storage Domain contains OVF_STORE disks, but attached to a Data Center with version lower the 3.5. What is your opinion about this? Do you think it sounds like a logical behavior or maybe this solution is better or you have other suggestions?
Importing an existing domain should be possible, but we should not fail on actions we know cannot work (force detaching, downloading OVFs). In this case, we should have an audit log with the proper warning.
Checked on version v3.5 13.6 Moving to Verified
RHEV-M 3.5.0 has been released, closing this bug.