Bug 2017625
| Summary: | Selecting a default migration network in the web console displays two networks with the same name in different namespaces | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Migration Toolkit for Virtualization | Reporter: | kpunwatk | ||||||
| Component: | User Experience | Assignee: | Mike Turley <mturley> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Igor Braginsky <ibragins> | ||||||
| Severity: | medium | Docs Contact: | Avital Pinnick <apinnick> | ||||||
| Priority: | medium | ||||||||
| Version: | 2.2.0 | CC: | fbladilo, fdupont, istein | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | 2.2.0 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2021-12-09 19:20:59 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
Created attachment 1837480 [details]
Select Migration Network Screenshot
This is trickier than I realized initially. My initial thought was that we should just show the namespaces in the network selection and include the namespace in the unique identifier of the default transfer network. However, I recall now that the intended behavior is that you select a network by name, and then when creating a migration plan, any target namespace containing a network with that name will use that as the default transfer network. If that is the intention, it seems the fix here would be instead to deduplicate the network names in the list. In the example of this screenshot, instead of having only one of those ovn-kubernetes1 networks checked but both displayed, we would display only one. Namespace would continue to not be part of the logic of selecting default transfer networks at the provider level, only network names. @fdupont can you confirm the desired behavior here? I do confirm that it is the desired behavior. Verified this bug on MTV 2.2.0-80, now when selecting default migration network on OCP side I could see only network from openshift-mtv namespace, which looks good for me. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (MTV 2.2.0 Images), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2021:5066 |
Created attachment 1837479 [details] Screenshot of Default migration network Description of problem: Select a "Default migration network" for the Openshift Virtualization provider. There are two networks with same Name on "different Target Namespaces". When click/select any one of them both gets selected as the default migration network. (Screenshots are Attached) Target Namespaces/ networks: 1. default / ovn-kubernetes1 2. openshift-mtv / ovn-kubernetes1 Version-Release number of selected component (if applicable): MTV-2.2.0-63 CNV-4.9.0-249 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: