Description of problem: I exported jb-rh6-x64 VM in 'Default' DC which contained snapshots. Then I dettached export domain and attached it to 'tmp' DC which is managed by same RHEVM. I wanted to import jb-rh6-x64 into 'tmp' DC and then popup windows shows me both 'Collapse Snapshots' and 'Clone' checkboxes checked. This "feature" which is silly in my option (not possible to have same VM names in different DCs) forces cloning of the vm so I would get 'Import Conflict' window to rename the importing VM. But this also forces collapsing snapshots, so I would lose snapshots. And this loosing of snapshots is super annoying. Version-Release number of selected component (if applicable): sf13.1 How reproducible: 100% Steps to Reproduce: 1. have 2 DCs 2. export a VM with snapshots to an export domain which you would "share" between DCs 3. try to import the exported VM on other DC and see window for collapse snapshots/clone "results" Actual results: due to existing VM name on the RHEVM env, import funcionality forces me to lose snapshots Expected results: if you won't solve name collision on the env itself now, then you should make some distinguishion between DCs and make something to prevent loosing of snapshots for "known" importing VMs Additional info: VM name uniqueness for whole RHEVM env is really annoying but this is another topis and I've opened RFE for it - BZ912263
IIUC this is about not collapsing snapshots on import. Not sure if this is currently possible, Ayal?
(In reply to comment #1) > IIUC this is about not collapsing snapshots on import. Not sure if this is > currently possible, Ayal? It is not, that is why it is marked as improvement above.
*** Bug 1161211 has been marked as a duplicate of this bug. ***
Can you do this with import data domain?
We currently can't do that, this need to be fixed for export and also for import since they both use the same logic on import. I think that this bug https://bugzilla.redhat.com/1431535 is also related to this issue
We will not be fixing this for the export domain. I'm changing this bug's summary to reflect the fix in the data domain.
The underlying requirement here is either to rewrite the chain or to allow the same chain in two DCs. Both are quite a lot of work, and I question the benefit. Propose removing from 4.3.
Closing old RFEs. If needed, please reopen and explain why.