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

Existing IP cannot be assigned to Virtual Machine or Device #1311

New Issue
Closed
opened 2025-12-29 16:31:20 +01:00 by adam · 4 comments
adam commented 2025-12-29 16:31:20 +01:00
Owner
Copy Link

Originally created by @martink2 on GitHub (Oct 15, 2017).

Issue type

[ ] Feature request
[x] Bug report
[ ] Documentation

Environment

  • Python version: 2.7.12
  • NetBox version: 2.2.1

Description

Existing IP's without a Device or VM assignment can't be assigned anymore.

When using the + Sign on the interface device the assignment is preset to the current device/vm.
Putting the already existing IP in as address results in the expected duplicate failure.
The edit form for existing IP's does not have an option to assign to a device / vm either.

Editing an already assigned IP gives the option to change the interface but not the device it is associated with.

Originally created by @martink2 on GitHub (Oct 15, 2017). <!-- Before opening a new issue, please search through the existing issues to see if your topic has already been addressed. Note that you may need to remove the "is:open" filter from the search bar to include closed issues. Check the appropriate type for your issue below by placing an x between the brackets. If none of the below apply, please raise your issue for discussion on our mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please note that issues which do not fall under any of the below categories will be closed. ---> ### Issue type [ ] Feature request <!-- Requesting the implementation of a new feature --> [x] Bug report <!-- Reporting unexpected or erroneous behavior --> [ ] Documentation <!-- Proposing a modification to the documentation --> <!-- Please describe the environment in which you are running NetBox. (Be sure to verify that you are running the latest stable release of NetBox before submitting a bug report.) --> ### Environment * Python version: 2.7.12<!-- Example: 3.5.4 --> * NetBox version: 2.2.1<!-- Example: 2.1.3 --> <!-- BUG REPORTS must include: * A list of the steps needed to reproduce the bug * A description of the expected behavior * Any relevant error messages (screenshots may also help) FEATURE REQUESTS must include: * A detailed description of the proposed functionality * A use case for the new feature * A rough description of any necessary changes to the database schema * Any relevant third-party libraries which would be needed --> ### Description Existing IP's without a Device or VM assignment can't be assigned anymore. When using the + Sign on the interface device the assignment is preset to the current device/vm. Putting the already existing IP in as address results in the expected duplicate failure. The edit form for existing IP's does not have an option to assign to a device / vm either. Editing an already assigned IP gives the option to change the interface but not the device it is associated with.
adam closed this issue 2025-12-29 16:31:20 +01:00
adam commented 2025-12-29 16:31:21 +01:00
Author
Owner
Copy Link

@lae commented on GitHub (Oct 16, 2017):

I'm affected by this, too, but this seems like it would have been an intentional change...?

@lae commented on GitHub (Oct 16, 2017): I'm affected by this, too, but this seems like it would have been an intentional change...?
adam commented 2025-12-29 16:31:22 +01:00
Author
Owner
Copy Link

@InsaneSplash commented on GitHub (Oct 16, 2017):

I am also not able to assign an IP to an existing device as there is no option to select the device and interface. When you add an IP to an interface through a device it works fine.

@InsaneSplash commented on GitHub (Oct 16, 2017): I am also not able to assign an IP to an existing device as there is no option to select the device and interface. When you add an IP to an interface through a device it works fine.
adam commented 2025-12-29 16:31:22 +01:00
Author
Owner
Copy Link

@InsaneSplash commented on GitHub (Oct 16, 2017):

Help :)

Missing interface assignment:

image

@InsaneSplash commented on GitHub (Oct 16, 2017): Help :) Missing interface assignment: ![image](https://user-images.githubusercontent.com/16985649/31615294-6bef2a46-b289-11e7-9855-fd4c0cd525ab.png)
adam commented 2025-12-29 16:31:22 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 16, 2017):

Duplicate of #1512

@jeremystretch commented on GitHub (Oct 16, 2017): Duplicate of #1512
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#1311
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?