Skip to content
This repository has been archived by the owner on Jul 21, 2023. It is now read-only.

Multiple networks with the same name appear for target provider for infrastructure mappings #257

Closed
bthurber opened this issue Apr 29, 2018 · 11 comments
Assignees
Projects

Comments

@bthurber
Copy link

BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1572169

Example: ovirtmgmt for a single target appears twice. 2 hosts enabled for the RHV provider with the conversion host role.

@bthurber
Copy link
Author

bthurber commented May 24, 2018

@priley86 @AparnaKarve this looks like a similar issue Miguel is having in his Ravello env. I think our solution here is going to be the same as for source networks...filter duplicate names in the UI.

@bthurber
Copy link
Author

screenshot from 2018-05-23 23-06-35

@priley86
Copy link
Member

priley86 commented Jun 1, 2018

@AparnaKarve is looking into this and will pull in the database from that environment...

@JPrause
Copy link
Member

JPrause commented Jun 18, 2018

@miq-bot add_label blocker

@JPrause
Copy link
Member

JPrause commented Jun 20, 2018

@AparnaKarve did you have an update on this PR.

@AparnaKarve
Copy link
Contributor

@JPrause I don't, atm.

We are currently waiting on a specific input from the RHV team regarding the Network deduplication.
Once @agrare hears back from them, we will have a plan on how to proceed on this.
Thanks.

@agrare
Copy link
Member

agrare commented Jun 21, 2018

@AparnaKarve I confirmed with RHV that uid_ems can be used to unique lans.

@AparnaKarve
Copy link
Contributor

Thanks @agrare !
Since most of our discussion on this topic is in #281, I have a comment there and just need you to confirm the mapping structure #281 (comment)

@priley86
Copy link
Member

Cool - we are using uid_ems to dedupe networks in the Infra Mapping list view as well already so it sounds like merging #404 will resolve this once and for all...

@AllenBW AllenBW added this to Backlog in v2v UI Jun 26, 2018
@JPrause
Copy link
Member

JPrause commented Jul 3, 2018

Any update on this PR. We have an upcoming build on July 10

@priley86
Copy link
Member

priley86 commented Jul 3, 2018

I believe this issue can be closed now. We are using the uid_ems to uniquely identify lans now, however to fully qualify this, we should also include the provider & cluster when uniquely identifying. If these aren't included, we risk a small edge case mentioned in #455. I'm looking at this currently.

@priley86 priley86 closed this as completed Jul 3, 2018
v2v UI automation moved this from Backlog to Done Jul 3, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
v2v UI
  
Done
Development

No branches or pull requests

6 participants