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

When bulk adding ips via a prefix, VRF should default to that of the prefix #1778

Closed
explody opened this issue Dec 16, 2017 · 2 comments
Closed
Labels
type: bug A confirmed report of unexpected behavior in the application

Comments

@explody
Copy link
Contributor

explody commented Dec 16, 2017

Issue type

[ ] Feature request
[ X ] Bug report
[ ] Documentation

Environment

  • Python version: 3.5.2
  • NetBox version: 2.2.8-dev (HEAD)

Description

When one navigates to a prefix and clicks "Add an IP address", the single-ip form defaults to setting the VRF to the current VRF of the prefix. However, if one switches to the 'Bulk Add' tab, the VRF selection resets to "Global".

Instead, it should default to the VRF of the prefix, as with the single-IP form.

Just follow the steps described to reproduce (confirmed on 2.2.7-dev - 2.2.8-dev)

screen shot 2017-12-15 at 8 10 44 pm

@explody
Copy link
Contributor Author

explody commented Dec 16, 2017

Minor correction, 'Global' may be a VRF we added, I don't recall. But, just checked this on a different vanilla instance and it defaulted to '---------'. In both cases, it's the default VRF option and not the one specified in the query args.

explody added a commit to explody/netbox that referenced this issue Dec 16, 2017
This will set initial values for visible bulk-add form fields from query args.
jeremystretch added a commit that referenced this issue Dec 20, 2017
@jeremystretch
Copy link
Member

Fixed in #1780

@jeremystretch jeremystretch added the type: bug A confirmed report of unexpected behavior in the application label Dec 20, 2017
@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
type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

2 participants