Skip to content
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

Unique IP space enforcement cannot be loosened for shared/virtual IPs #2501

Closed
knobix opened this issue Oct 8, 2018 · 0 comments · Fixed by #2502
Closed

Unique IP space enforcement cannot be loosened for shared/virtual IPs #2501

knobix opened this issue Oct 8, 2018 · 0 comments · Fixed by #2502

Comments

@knobix
Copy link
Contributor

knobix commented Oct 8, 2018

Environment

  • Python version: 3.6.6
  • NetBox version: 2.4.6

Steps to Reproduce

  • Create a new VRF (e.g. Example)
  • Add an IP-address (e.g. 192.168.0.1/24) and set the role to VIP in the newly created VRF
  • Add the same IP-address again and set the role to VIP in the newly created VRF

Expected Behavior

  • The second shared IP-address that is a duplicate should have been added to the VRF without any errors.

Observed Behavior

  • The message "Duplicate IP address found in VRF Example (Example123): 192.168.0.1/24"
jeremystretch pushed a commit that referenced this issue Nov 5, 2018
Fix the handling of shared IPs (VIP, VRRF, etc.) when unique IP space enforcement is set.

Add parentheses for the logical OR-statement to make the evaluation valid.

Fixes: #2501
jeremystretch added a commit that referenced this issue Nov 5, 2018
@lock lock bot locked as resolved and limited conversation to collaborators Jan 17, 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

Successfully merging a pull request may close this issue.

1 participant