Bug 1775385 - Mapping Wizard: OSP conversion host warning check is too broad, needs to look at specific providers
Summary: Mapping Wizard: OSP conversion host warning check is too broad, needs to look...
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: V2V
Version: 5.11.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: GA
: 5.11.z
Assignee: Mike Turley
QA Contact: Sudhir Mallamprabhakara
Red Hat CloudForms Documentation
Depends On:
TreeView+ depends on / blocked
Reported: 2019-11-21 20:41 UTC by Mike Turley
Modified: 2019-11-27 03:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Category: Bug
Cloudforms Team: V2V
Target Upstream Version:

Attachments (Terms of Use)

Description Mike Turley 2019-11-21 20:41:18 UTC
See: https://github.com/ManageIQ/manageiq-v2v/issues/1069

When we implemented OSP target support, we made a mistake (in #812) in the logic that detects whether the user needs to be warned that there is no conversion host configured.

Currently, if there are no OSP conversion hosts anywhere the appliance can find, the UI displays a warning on the clusters step of the wizard reading "No OpenStack conversion hosts are configured. You can continue to create an infrastructure mapping, but you must configure a conversion host before migration execution."

However, this warning just checks whether OSP conversion hosts exist at all, it does not take into account which provider/EMS they reside in. If the user has more than one OSP provider configured, they could in theory have a conversion host in provider A (and therefore not see the warning), but create a mapping to provider B which would fail.

The conversion host warning for OSP needs to be similar to the one for RHV (a warning icon on each target cluster in the list), but instead of looking for the conversion host in that specific target cluster/project, it should look for a conversion host with the same EMS id as that target cluster/project.

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