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

Interface connection fills out some A side and some B side #7753

New Issue
Closed
opened 2025-12-29 20:27:49 +01:00 by adam · 2 comments
adam commented 2025-12-29 20:27:49 +01:00
Owner
Copy Link

Originally created by @wxnarwhal on GitHub (Mar 13, 2023).

NetBox version

v3.4.5

Python version

3.8

Steps to Reproduce

  1. Go to interface or port
  2. click "Connect" and select interface.

Expected Behavior

Expected behavior should be that all information from the interface I selected should populate on the A side. Before I make the connection NetBox has no idea if the the B side is in the same room, or even the same site.

Observed Behavior

Device and port/interface populate on A side, but the site and rack populate on the B side.

Verified on the demo site, one site I have running v3.4.5, and one site I have running v3.3.7.

Originally created by @wxnarwhal on GitHub (Mar 13, 2023). ### NetBox version v3.4.5 ### Python version 3.8 ### Steps to Reproduce 1. Go to interface or port 2. click "Connect" and select interface. ### Expected Behavior Expected behavior should be that all information from the interface I selected should populate on the A side. Before I make the connection NetBox has no idea if the the B side is in the same room, or even the same site. ### Observed Behavior Device and port/interface populate on A side, but the site and rack populate on the B side. Verified on the demo site, one site I have running v3.4.5, and one site I have running v3.3.7.
adam added the type: bug label 2025-12-29 20:27:49 +01:00
adam closed this issue 2025-12-29 20:27:50 +01:00
adam commented 2025-12-29 20:27:50 +01:00
Author
Owner
Copy Link

@wxnarwhal commented on GitHub (Mar 13, 2023):

Attaching screenshot.
Screenshot_20230313_105711

@wxnarwhal commented on GitHub (Mar 13, 2023): Attaching screenshot. ![Screenshot_20230313_105711](https://user-images.githubusercontent.com/10369715/224793163-56ef1fb4-2ad3-4692-90fb-7bd0121e622b.png)
adam commented 2025-12-29 20:27:50 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 16, 2023):

The cable creation form has been significantly simplified for the upcoming v3.5 release. The region, site group, site, location, and rack fields have been removed in favor of a device selector widget (see #10054).

@jeremystretch commented on GitHub (Mar 16, 2023): The cable creation form has been significantly simplified for the upcoming v3.5 release. The region, site group, site, location, and rack fields have been removed in favor of a device selector widget (see #10054).
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: 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#7753
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?