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

ConsolePort and ConsoleServerPort disconnect generates inconsistent webhooks. #3665

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

Originally created by @karrots on GitHub (May 9, 2020).

Originally assigned to: @jeremystretch on GitHub.

Environment

  • Python version: 3.7.7
  • NetBox version: 2.8.3

Steps to Reproduce

  1. Disable any installed plugins by commenting out the PLUGINS setting in
    configuration.py.
  2. Create a device with a console port
  3. Create a device with a console server port
  4. Create webhook attached to DCIM > console server port
    4.1. Type: update
    4.2. Method PUT (though this doesn't matter)
  5. Navigate to either the console port or console server port and click the green connect button.
  6. Disconnect the two ports

Expected Behavior

  1. Single webhook invocation
  2. connected_endpoint, connection_status, and cable filled fully with data or fully null

Observed Behavior

Connect operation triggers 3 identical webhook invocations.

Remove cable operation triggered from the ConsolePort port will create 2 invocations the first showing update with cable set to null but still showing the connected_endpoint and connection_status with data.
The second showing connected_endpoint, connection_status, and cable as null (disconnected).

Remove cable operation triggered from the ConsoleServerPort port will cause one invocation with data showing cable and connected_endpoint but the connection_status still shows as connected.

Originally created by @karrots on GitHub (May 9, 2020). Originally assigned to: @jeremystretch on GitHub. <!-- 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.7 * NetBox version: 2.8.3 <!-- 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. Disable any installed plugins by commenting out the `PLUGINS` setting in `configuration.py`. 2. Create a device with a console port 3. Create a device with a console server port 4. Create webhook attached to **DCIM > console server port** 4.1. Type: update 4.2. Method PUT (though this doesn't matter) 5. Navigate to either the console port or console server port and click the green connect button. 6. Disconnect the two ports <!-- What did you expect to happen? --> ### Expected Behavior 1. Single webhook invocation 2. `connected_endpoint`, `connection_status`, and `cable` filled fully with data or fully `null` <!-- What happened instead? --> ### Observed Behavior Connect operation triggers 3 identical webhook invocations. Remove cable operation triggered from the `ConsolePort` port will create 2 invocations the first showing update with `cable` set to `null` but still showing the `connected_endpoint` and `connection_status` with data. The second showing `connected_endpoint`, `connection_status`, and `cable` as `null` (disconnected). Remove cable operation triggered from the `ConsoleServerPort` port will cause one invocation with data showing `cable` and `connected_endpoint` but the `connection_status` still shows as connected.
adam added the type: bugstatus: accepted labels 2025-12-29 18:30:28 +01:00
adam closed this issue 2025-12-29 18:30:28 +01:00
adam commented 2025-12-29 18:30:28 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 11, 2020):

Please specify the stable NetBox release on which this issue may be replicated.

@jeremystretch commented on GitHub (May 11, 2020): Please specify the stable NetBox release on which this issue may be replicated.
adam commented 2025-12-29 18:30:28 +01:00
Author
Owner
Copy Link

@karrots commented on GitHub (May 11, 2020):

v2.8.3

@karrots commented on GitHub (May 11, 2020): v2.8.3
adam commented 2025-12-29 18:30:28 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 8, 2020):

I need to revisit this for v2.10 now that #4900 has been completed.

@jeremystretch commented on GitHub (Oct 8, 2020): I need to revisit this for v2.10 now that #4900 has been completed.
adam commented 2025-12-29 18:30:28 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 13, 2020):

This has been resolved as part of the work on #4900 for the upcoming v2.10 release.

@jeremystretch commented on GitHub (Nov 13, 2020): This has been resolved as part of the work on #4900 for the upcoming v2.10 release.
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 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#3665
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?