Skip to content

Unable to assign IP to interface #3757

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
abrahamvegh opened this issue Dec 12, 2019 · 1 comment · Fixed by #3764
Closed

Unable to assign IP to interface #3757

abrahamvegh opened this issue Dec 12, 2019 · 1 comment · Fixed by #3764
Assignees
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@abrahamvegh
Copy link
Contributor

Environment

  • Python version: 3.7.3
  • NetBox version: 2.6.8

Steps to Reproduce

  1. From a Device with an Interface, click the ‘Add IP address’ button
  2. Click the ‘Assign IP’ tab
  3. Search for an IP
  4. Click an IP in the search results

Expected Behavior

The IP address link should contain the ID of the interface we are attempting to assign to.

Observed Behavior

For IPs not currently assigned to an interface, the interface URL parameter is empty.
For IPs currently assigned to an interface, the interface URL parameter is the ID of the interface it is currently assigned to, not the one we are attempting to assign to.

Notes

It appears this was introduced by #3687. I’m not familiar enough with Python or the codebase to determine what the correct fix would be that would satisfy both the bug being addressed by that PR and this regression. In the meantime, it is still possible to assign an IP by manually inserting the ID of the correct interface into the link URL.

@kobayashi kobayashi self-assigned this Dec 13, 2019
@kobayashi
Copy link
Contributor

Thank you for letting me know.
Yes, that PR fixed to see correct ip assign information (device -> interface -> ip address), but makes this bug. I am taking this issue.

@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application labels Dec 13, 2019
@kobayashi kobayashi mentioned this issue Dec 13, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Mar 17, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants