starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Unable to assign IP Address to interface #3071

New Issue
Closed
opened 2025-12-29 18:25:21 +01:00 by adam · 1 comment
adam commented 2025-12-29 18:25:21 +01:00
Owner
Copy Link

Originally created by @clatini on GitHub (Dec 15, 2019).

Environment

  • Python version: 3.7.3
  • NetBox version: 2.6.8

Steps to Reproduce

  1. In IPAM/IP Addresses, create a new IP Address; populate only mandatory fields (Address, Status);
  2. In Devices, select an existing device, then select an existing interface and select '+' icon to add an IP Address;
  3. Now, click 'Assign IP' Tab, then search for the previously created IP Address;
  4. In the list, the IP Address link is something like this:

http://netbox.test.local/ipam/ip-addresses/395/edit/?interface=&return_url=/ipam/ip-addresses/assign/

Expected Behavior

The 'interface' field in the URL must reference the interface id

Observed Behavior

The 'interface' field is blank

Note: If the ip address is already assigned, the 'interface' field is correctly referenced.

Originally created by @clatini on GitHub (Dec 15, 2019). <!-- NOTE: This form is only for reproducible bugs. If you need assistance with NetBox installation, or if you have a general question, DO NOT open an issue. Instead, post to our mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.7.3 <!-- Example: 3.5.4 --> * NetBox version: 2.6.8 <!-- Example: 2.5.2 --> <!-- Describe in detail the exact steps that someone else can take to reproduce this bug using the current stable release of NetBox (or the current beta release where applicable). Begin with the creation of any necessary database objects and call out every operation being performed explicitly. If reporting a bug in the REST API, be sure to reconstruct the raw HTTP request(s) being made: Don't rely on a wrapper like pynetbox. --> ### Steps to Reproduce 1. In IPAM/IP Addresses, create a new IP Address; populate only mandatory fields (Address, Status); 2. In Devices, select an existing device, then select an existing interface and select '+' icon to add an IP Address; 3. Now, click 'Assign IP' Tab, then search for the previously created IP Address; 4. In the list, the IP Address link is something like this: http://netbox.test.local/ipam/ip-addresses/395/edit/?interface=&return_url=/ipam/ip-addresses/assign/ <!-- What did you expect to happen? --> ### Expected Behavior The 'interface' field in the URL must reference the interface id <!-- What happened instead? --> ### Observed Behavior The 'interface' field is blank Note: If the ip address is already assigned, the 'interface' field is correctly referenced.
adam closed this issue 2025-12-29 18:25:21 +01:00
adam commented 2025-12-29 18:25:22 +01:00
Author
Owner
Copy Link

@kobayashi commented on GitHub (Dec 16, 2019):

Thank you for opening this issue. This is duplicated issue with #3757 which was fixed. Please see it for the detail.

@kobayashi commented on GitHub (Dec 16, 2019): Thank you for opening this issue. This is duplicated issue with #3757 which was fixed. Please see it for the detail.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#3071
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?