Created attachment 1433255 [details] screenshot Description of problem: When trying to map a target datastore with size lower than the source datastore, MIQ blocks the mapping with error: "The size of the selected source datastores exceeds the available space in the target datastore". This check should be added to the migration job itself, and needs to be calculated per selected VM's total size. Version-Release number of selected component (if applicable): MIQ master.20180504232106_a937a31 How reproducible: 100% Steps to Reproduce: 1. Try to map target DS to bigger source DS in size. Actual results: Error and mapping is blocked. Expected results: Should not block the mapping. Additional info:
Changing the severity to high. Adding a testblocker since it blocks nsimsolo from running a test with his VMWare and RHV environments.
Verified this still exists . Upstream issue here: https://github.com/ManageIQ/miq_v2v_ui_plugin/issues/345
This is currently blocking us from testing the environment. Our target DS got filled and we reinstalled MIQ, thus mapping cannot be done now.
(In reply to Mor from comment #4) > This is currently blocking us from testing the environment. Our target DS > got filled and we reinstalled MIQ, thus mapping cannot be done now. As a workaround can you clean up your target datastore to resume testing?
At the end, we ended up creating a new DS for the process and resumed testing. So I'm switching back to HIGH.
Can I verify this but currently? Is 5.9.4.x available for V2V testing? We currently run on 5.9.3.x.
* correction: I can verify this, but currently is 5.9.4x available for V2V testing? We currently run on 5.9.3.x.
On 5.10.0.2 I observed that there is no more Validations on Datastore sizes. User is free to choose any source/target datastores, no size checking/restrictions.
Verified by CFME functional QE.
*** Bug 1614470 has been marked as a duplicate of this bug. ***