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

No ip_address field in services bulk import view #3920

New Issue
Closed
opened 2025-12-29 18:32:05 +01:00 by adam · 3 comments
adam commented 2025-12-29 18:32:05 +01:00
Owner
Copy Link

Originally created by @clearly-tyler-whitney on GitHub (Jul 29, 2020).

Environment

  • Python version: 3.7.8
  • NetBox version: 2.8.8

Steps to Reproduce

  1. Navigate to /ipam/services/import/ in the webGUI.
  2. Try to import service data CSV w/ IP assignments included, as is possible during single assignment
    (i.e., /virtualization/virtual-machines//services/assign/ or /dcim/devices//services/assign/)
  3. Realize this CSV column is not a thing.
  4. Weep softly (optional).
  5. Add IPs by hand.

Expected Behavior

To be able to specify IP address info during services data import.

Observed Behavior

Self explanatory.

Originally created by @clearly-tyler-whitney on GitHub (Jul 29, 2020). <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. 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, and that any plugins have been disabled. --> ### Environment * Python version: 3.7.8 * NetBox version: 2.8.8 <!-- Describe in detail the exact steps that someone else can take to reproduce this bug using the current stable release of NetBox. 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 client library such as pynetbox. --> ### Steps to Reproduce 1. Navigate to /ipam/services/import/ in the webGUI. 2. Try to import service data CSV w/ IP assignments included, as is possible during single assignment (i.e., /virtualization/virtual-machines/<id>/services/assign/ or /dcim/devices/<id>/services/assign/) 3. Realize this CSV column is not a thing. 4. Weep softly (optional). 5. Add IPs by hand. <!-- What did you expect to happen? --> ### Expected Behavior To be able to specify IP address info during services data import. <!-- What happened instead? --> ### Observed Behavior Self explanatory.
adam closed this issue 2025-12-29 18:32:05 +01:00
adam commented 2025-12-29 18:32:05 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 30, 2020):

This would need to be a feature request, not a bug report, as this behavior is expected. Please consider opening a feature request if you'd like to propose a specific implementation to support this.

@jeremystretch commented on GitHub (Jul 30, 2020): This would need to be a feature request, not a bug report, as this behavior is expected. Please consider opening a feature request if you'd like to propose a specific implementation to support this.
adam commented 2025-12-29 18:32:05 +01:00
Author
Owner
Copy Link

@clearly-tyler-whitney commented on GitHub (Jul 30, 2020):

I will submit a feature request for this. Will you clarify why this is the intended behavior? It seems counter-intuitive, at least to me.

@clearly-tyler-whitney commented on GitHub (Jul 30, 2020): I will submit a feature request for this. Will you clarify why this is the intended behavior? It seems counter-intuitive, at least to me.
adam commented 2025-12-29 18:32:06 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 30, 2020):

The problems will likely become evident in the course of devising a proposed solution, but I'm happy to explain further in a FR.

@jeremystretch commented on GitHub (Jul 30, 2020): The problems will likely become evident in the course of devising a proposed solution, but I'm happy to explain further in a FR.
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#3920
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?