Fedora Account System
Red Hat Associate
Red Hat Customer
Created attachment 1615564 [details] issue.mp4 Description of problem: If your cluster is empty then it should tell that 'No datastore is present' instead of it is giving 'All source datastores have been mapped' Version-Release number of selected component (if applicable): 5.11.0.23 How reproducible: 100% Steps to Reproduce: 1. Map EmptyCluster with OSP project 2. On 'Map Storage' tab of modal, you will find 'All source datastores have been mapped.' in source selection box. Actual results: Should not get that Note. Expected results: Should get note which says there is no datastore. Additional info: Related to https://bugzilla.redhat.com/show_bug.cgi?id=1677677#c0.
Hey Brett - Looking at this BZ with Mike and we have a question. Can a cluster ever exist with no datastores? Right now, we block the user from continuing in the mapping wizard until at least one datastore from each source cluster is mapped. Trying to decide if this is a UI bug? Y-Tale ran across this in a test and we're not sure if it's a valid use case. Thanks.
(In reply to vconzola from comment #6) > Hey Brett - Looking at this BZ with Mike and we have a question. Can a > cluster ever exist with no datastores? Right now, we block the user from > continuing in the mapping wizard until at least one datastore from each > source cluster is mapped. Trying to decide if this is a UI bug? Y-Tale ran > across this in a test and we're not sure if it's a valid use case. Thanks. Without datastores there are no VM's or VM templates. Invalid use case IMO.
Is it technically possible to have a cluster without any VMs (and therefore without any datastores) though? If so, the error messaging should still be improved if a user tries to select an empty cluster like this.
(In reply to Mike Turley from comment #8) > Is it technically possible to have a cluster without any VMs (and therefore > without any datastores) though? If so, the error messaging should still be > improved if a user tries to select an empty cluster like this. Being empty negates the whole reason to try and initiate a migration however. The other side of this is if there is something incorrect within CloudForms causing a populated/configured VMware env to not display any clusters or datastores. That would be the only "valid" reason to display an error message.
PR: https://github.com/ManageIQ/manageiq-v2v/pull/1090