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

Force Interface creation before allowing IP assignment #371

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

Originally created by @LordBoBCUP on GitHub (Aug 18, 2016).

I've noticed, when trying to assign an IP address to a device, if there are no interfaces assigned to it, you are still able to load the assign IP form. You can enter in the IP, VRF etc, and when you click create it prompts you to select an interface of which there are none. There should be logic either flagging a warning, or, forcing you to the add interface page if there isn't at least 1 free interface that the IP can be assigned to when you first click on the add IP address button on the device view page. This is in v1.5.1.

Originally created by @LordBoBCUP on GitHub (Aug 18, 2016). I've noticed, when trying to assign an IP address to a device, if there are no interfaces assigned to it, you are still able to load the assign IP form. You can enter in the IP, VRF etc, and when you click create it prompts you to select an interface of which there are none. There should be logic either flagging a warning, or, forcing you to the add interface page if there isn't at least 1 free interface that the IP can be assigned to when you first click on the add IP address button on the device view page. This is in v1.5.1.
adam added the type: feature label 2025-12-29 16:21:25 +01:00
adam closed this issue 2025-12-29 16:21:25 +01:00
adam commented 2025-12-29 16:21:26 +01:00
Author
Owner
Copy Link

@iamdadmin commented on GitHub (Sep 2, 2016):

There are several places when the same check could be added; just a few examples:

  1. Add a device type before device.
  2. Add a manufacturer before a device type.
  3. Anywhere else you have a required field from a user created table.
@iamdadmin commented on GitHub (Sep 2, 2016): There are several places when the same check could be added; just a few examples: 1. Add a device type before device. 2. Add a manufacturer before a device type. 3. Anywhere else you have a required field from a user created table.
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 type: feature
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#371
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?