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

Inconsistent behaviour with Label on front port when using range #11053

New Issue
Closed
opened 2025-12-29 21:39:41 +01:00 by adam · 0 comments
adam commented 2025-12-29 21:39:41 +01:00
Owner
Copy Link

Originally created by @LabelWriter450 on GitHub (Apr 17, 2025).

Originally assigned to: @jeremystretch on GitHub.

Deployment Type

Self-hosted

NetBox Version

v4.2.7

Python Version

3.10

Steps to Reproduce

  1. Go to Device
  2. Add "Add a new front Port"
  3. Select Device
  4. Give name [0-9]
  5. Give Label without range
  6. Assign Type
  7. Assign Rear Port

Expected Behavior

The front connections should be added with the same label

Observed Behavior

Error: "The provided pattern specifies 1 values, but 10 are expected."

It is not possible to add several front ports through range with the same label.
But it is possible to edit all of them at once afterwards and set the same label for all of them.

Image
Image

Follow up Issue of #19041

Originally created by @LabelWriter450 on GitHub (Apr 17, 2025). Originally assigned to: @jeremystretch on GitHub. ### Deployment Type Self-hosted ### NetBox Version v4.2.7 ### Python Version 3.10 ### Steps to Reproduce 1. Go to Device 2. Add "Add a new front Port" 3. Select Device 4. Give name [0-9] 5. **Give Label without range** 6. Assign Type 7. Assign Rear Port ### Expected Behavior The front connections should be added with the **same** label ### Observed Behavior Error: "The provided pattern specifies 1 values, but 10 are expected." It is not possible to add several front ports through range with the same label. But it is possible to edit all of them at once afterwards and set the same label for all of them. ![Image](https://github.com/user-attachments/assets/d85f70ca-5ee8-4a3d-ae9c-c8a107e46cef) ![Image](https://github.com/user-attachments/assets/be270206-a059-4c9a-a179-c58a0d4a8efe) Follow up Issue of #19041
adam added the type: bugstatus: acceptedseverity: low labels 2025-12-29 21:39:41 +01:00
adam closed this issue 2025-12-29 21:39:41 +01:00
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 severity: low status: accepted type: bug
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#11053
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?