Created attachment 1535224 [details]
Description of problem:
1. Enhance error reporting for empty clusters - If your cluster is empty then it should tell in datastore that no 'datastore is present' instead of 'All source datastores have been mapped' (first video)
2. Clusters selections issues on map - Lets say if you two clusters X and Y (Y is empty), and you selected both at source, click next .. found two behaviors after that at datastore selection of modal..
a. by default Y clusters get selected but despite it is empty, X's datastores shows up.
b. you will get option to select clusters but you won't find any of the datastore there on both selections. (second video)
Version-Release number of selected component (if applicable):
Used QE's vsphere60-ims
Created attachment 1535225 [details]
Please assess the impact of this issue and update the severity accordingly. Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity for a reminder on each severity's definition.
If it's something like a tracker bug where it doesn't matter, please set the severity to Low.
Wrongly placed priority instead of severity.
@Mike, do you think it's still an issue in recent versions ? If so, can you assess the complexity of fixing it, please ?
@YTale, do you have an appliance I can access which is in a state where this problem can be reproduced? I would like to get a database dump from that appliance to test against locally.
This appears to be non-trivial, it may be an issue related to how we handle filtering datastores, and Vince also said he'd like to mock up improved error messaging for this case. So I think we need to move this to 5.11 in the interest of time.
@mike, any news on this ? Did Vince and you revisit the error message display for this case ?
I was unable to reproduce this error.. @YTale, can you provide access to an appliance where this error is occurring? I'll need a dump of its database to develop against.
I don't think Vince and I revisited this from a design perspective either. I'm guessing it needs to go to 5.11.z.
YTale, for the error reporting piece of this, I'd still like to get access to an appliance which is showing that problem so I can develop a fix against real data.
This bug is fixed by https://github.com/ManageIQ/manageiq-v2v/pull/1033 which has been merged to master.