Bug 1597796 - [v2v] Source and Target Datastore Size restrictions should be removed
Summary: [v2v] Source and Target Datastore Size restrictions should be removed
Keywords:
Status: CLOSED DUPLICATE of bug 1595446
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.9.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: GA
: cfme-future
Assignee: Dan Clarizio
QA Contact: Kedar Kulkarni
URL:
Whiteboard: v2v
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-03 15:42 UTC by Kedar Kulkarni
Modified: 2018-07-03 15:56 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-07-03 15:56:14 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:
kkulkarn: automate_bug-


Attachments (Terms of Use)

Description Kedar Kulkarni 2018-07-03 15:42:04 UTC
Description of problem:
Source and Target Datastore Size restrictions should be removed from Infra mapping wizard. This is already implemented in 5.10.0.2, we need to backport this change before release. User may not be able to migrate VM from source to target even if there is space on target, if used space on source is more than available space on target. 

E.g. I am trying to migrate a 50GB VM from source which has used space 500GB, and target has available space 100GB, then ideally I should be able to migrate VM, irrespective of how much storage is used by source datastore. 

Version-Release number of selected component (if applicable):
5.9.3.4

How reproducible:
100% if your source storage is bigger or more utilized than available target space

Steps to Reproduce:
1.Add VMware and RHV provider
2.Open infra mapping wizard and navigate to Datastore page
3.

Actual results:
if source storage utilization is more that target available space, mapping won't let you proceed. 

Expected results:
I can map source to target without being blocked. Maybe provide a warning. Or remove it altogether as we have done in 5.10.0.2

Additional info:

Comment 2 Sudhir Mallamprabhakara 2018-07-03 15:56:14 UTC

*** This bug has been marked as a duplicate of bug 1595446 ***


Note You need to log in before you can comment on or make changes to this bug.