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

Rear Port bulk create Positions #2264

New Issue
Closed
opened 2025-12-29 17:24:18 +01:00 by adam · 4 comments
adam commented 2025-12-29 17:24:18 +01:00
Owner
Copy Link

Originally created by @MarcHagen on GitHub (Jan 6, 2019).

Environment

  • Python version: 3.6
  • NetBox version: v2.5.2

Steps to Reproduce

Bulk create a RearPort with
Name: RackB-A[1-12]
Type: any
Positions: 1

Expected Behavior

Bulk created
RackB-A1 - position 1,
RackB-A2 - position 2,
and so on.....

Observed Behavior

Bulk created
RackB-A1 - position 1,
RackB-A2 - position 1,
RackB-A3 - position 1,
and so on.....

Originally created by @MarcHagen on GitHub (Jan 6, 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.6 * NetBox version: v2.5.2 <!-- Describe in detail the steps that someone else can take to reproduce this bug using the current stable release of NetBox (or the current beta release where applicable). --> ### Steps to Reproduce Bulk create a RearPort with Name: RackB-A[1-12] Type: any Positions: 1 <!-- What did you expect to happen? --> ### Expected Behavior Bulk created RackB-A1 - position 1, RackB-A2 - position 2, and so on..... <!-- What happened instead? --> ### Observed Behavior Bulk created RackB-A1 - position 1, RackB-A2 - position 1, RackB-A3 - position 1, and so on.....
adam closed this issue 2025-12-29 17:24:18 +01:00
adam commented 2025-12-29 17:24:19 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 7, 2019):

This is expected behavior. The name pattern applies only to the name. Position identifiers are unique to their respective ports.

@jeremystretch commented on GitHub (Jan 7, 2019): This is expected behavior. The name pattern applies only to the name. Position identifiers are unique to their respective ports.
adam commented 2025-12-29 17:24:20 +01:00
Author
Owner
Copy Link

@MarcHagen commented on GitHub (Jan 7, 2019):

Oke thanks for the clarification, but if i have to make 32 rear ports, i must open every single one to update the position? Why is there a bulk option anyway then :/

@MarcHagen commented on GitHub (Jan 7, 2019): Oke thanks for the clarification, but if i have to make 32 rear ports, i must open every single one to update the position? Why is there a bulk option anyway then :/
adam commented 2025-12-29 17:24:20 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 7, 2019):

The positions for each rear port always start at one. You do not need to renumber them.

@jeremystretch commented on GitHub (Jan 7, 2019): The positions for each rear port always start at one. You do not need to renumber them.
adam commented 2025-12-29 17:24:20 +01:00
Author
Owner
Copy Link

@MarcHagen commented on GitHub (Jan 7, 2019):

Ah, know you what. I have read the docs now 20 times, i get it now...
I have a hard time figuring out text/theorie stuff to practical operations.
I'm sorry if this was any waste of time. But thank you 💯

@MarcHagen commented on GitHub (Jan 7, 2019): Ah, know you what. I have read the docs now 20 times, i get it now... I have a hard time figuring out text/theorie stuff to practical operations. I'm sorry if this was any waste of time. But thank you 💯
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#2264
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?