Skip to content

Prefix with role container does not show child prefixes correctly #3554

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
ziggekatten opened this issue Sep 29, 2019 · 6 comments
Closed

Prefix with role container does not show child prefixes correctly #3554

ziggekatten opened this issue Sep 29, 2019 · 6 comments

Comments

@ziggekatten
Copy link

ziggekatten commented Sep 29, 2019

Environment

  • Python version: 3.7.4
  • NetBox version: 2.6.5

Steps to Reproduce

  1. Add a prefix of type container 192.168.125.0/24
  2. Add a prefix of type Active 192.168.125.0/26
  3. Add a prefix of type Active 192.168.125.64/26
  4. Edit prefix 192.168.125.0/26 and assign to a VRF
  5. Edit prefix 192.168.125.64/26 and assign to another VRF

Expected Behavior

Adding two prefixes with assignment to separate VFRs:

192.168.125.0/24 and 192.168.125.64/26

In the prefixes UI I should now see the 192.168.1.0/24 with an small arrow indicating child prefixes

Klickin on the container prefix, i should have twe child prefixes

Capture1

Observed Behavior

As soon as I add one or the other prefix to a VRF, the prefix are not hidden under the container, it shows directly in the UI. Klicking on the container prefix however, shows (correctly) that there are two child prefixes.
Capture2

Capture3

@kobayashi
Copy link
Contributor

Allow indicator for child prefixes appears in prefixes list when same VRF is assigned to them.
What you want to do can be defined in Aggregate menu.
Try to create Aggregate with 192.168.125.0/24. Then assign 192.168.125.0/26 as VRF 10700 and 192.168.125.64/26 as VRF 10710 in the aggregate.

@ziggekatten
Copy link
Author

No, that does not solve the issue. As a service provider, we have several clients using the same 10.0.0.0/8 and 192.168.0.0/16, and aggregates can NOT have the same prefix more than once.

@kobayashi
Copy link
Contributor

Thanks to let me know about the detail.
I tested today with netbox version 2.6.5 and found that worked well.
Screenshot from 2019-09-30 22-20-45

Which netbox version are you using right now? So I can try with your version.

@ziggekatten
Copy link
Author

I’m running 2.6.5

@kobayashi
Copy link
Contributor

OK, I found this is reproduced not by one by one each but only by bulk importing.
Also found the same issue is already opened #2562. Please track that case.

@kobayashi
Copy link
Contributor

closed this issue due to duplication. Please refer #2562

@lock lock bot locked as resolved and limited conversation to collaborators Jan 15, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants