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

Power and console cables status isn't shown correctly #10399

New Issue
Closed
opened 2025-12-29 21:30:57 +01:00 by adam · 5 comments
adam commented 2025-12-29 21:30:57 +01:00
Owner
Copy Link

Originally created by @Pesk0v on GitHub (Oct 24, 2024).

Deployment Type

Self-hosted

Triage priority

N/A

NetBox Version

4.0.2

Python Version

3.12

Steps to Reproduce

The problem occurs only for console ports and power ports. Connected ports on the Power Ports, Power Outlets, Console Ports, Console Server Ports tabs are not highlighted in color, no matter what cable status set ('Installed' or 'Planned').

Expected Behavior

Right after a cable is created to connect two ports, the rows corresponding to connected ports are expected to be highlighted in green by default. The toggle should be orange and change cable status from 'Installed' to 'Planned'.

Observed Behavior

Once a cable for connection two either console or power ports has been created, the port (in tabs Power Ports, Power Outlets, Console Ports, Console Server Ports) which the cable is connected to is shown like it wouldn't be connected though the connection is correctly indicated in row. At that there is the 'Mark Installed' blue button in the port row.
image
When clicking on the button everything seems back to normality, i.e. the row is highlighted in green, and the blue toggle turns orange toggle switching port status into 'Mark Planned'. In other words the toggle gets working as expected, switching the cable status between 'Planned' and 'Installed' with the correct color highlighting of the port row.
But all rows corresponding to the connected ports are not highlighted again and everything returns to the abnormal state when pressing F5 (refresh screen) or reopening the tab.
Worth noting that interface ports are not affected by this problem.

Originally created by @Pesk0v on GitHub (Oct 24, 2024). ### Deployment Type Self-hosted ### Triage priority N/A ### NetBox Version 4.0.2 ### Python Version 3.12 ### Steps to Reproduce The problem occurs only for console ports and power ports. Connected ports on the Power Ports, Power Outlets, Console Ports, Console Server Ports tabs are not highlighted in color, no matter what cable status set ('Installed' or 'Planned'). ### Expected Behavior Right after a cable is created to connect two ports, the rows corresponding to connected ports are expected to be highlighted in green by default. The toggle should be orange and change cable status from 'Installed' to 'Planned'. ### Observed Behavior Once a cable for connection two either console or power ports has been created, the port (in tabs Power Ports, Power Outlets, Console Ports, Console Server Ports) which the cable is connected to is shown like it wouldn't be connected though the connection is correctly indicated in row. At that there is the 'Mark Installed' blue button in the port row. ![image](https://github.com/user-attachments/assets/1ec3849b-2b7b-4ecc-a25d-58a7dcf1d73e) When clicking on the button everything seems back to normality, i.e. the row is highlighted in green, and the blue toggle turns orange toggle switching port status into 'Mark Planned'. In other words the toggle gets working as expected, switching the cable status between 'Planned' and 'Installed' with the correct color highlighting of the port row. But all rows corresponding to the connected ports are not highlighted again and **everything returns to the abnormal state** when pressing F5 (refresh screen) or reopening the tab. Worth noting that interface ports are not affected by this problem.
adam added the type: bugpending closurestatus: revisions needednetbox labels 2025-12-29 21:30:57 +01:00
adam closed this issue 2025-12-29 21:30:57 +01:00
adam commented 2025-12-29 21:30:59 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (Oct 25, 2024):

@Pesk0v Thank you for the bug report, can you please add more reproduction steps to this. It's not clear in the steps to reproduce exactly what you are doing to see the problem.

Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports.

This is what I'm seeing:
PP:B117 | NetBox 2024-10-25 07-46-42

@arthanson commented on GitHub (Oct 25, 2024): @Pesk0v Thank you for the bug report, can you please add more reproduction steps to this. It's not clear in the steps to reproduce exactly what you are doing to see the problem. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports. This is what I'm seeing: ![PP:B117 | NetBox 2024-10-25 07-46-42](https://github.com/user-attachments/assets/01f9c763-4166-426e-a2b9-78d41bcaff54)
adam commented 2025-12-29 21:30:59 +01:00
Author
Owner
Copy Link

@Pesk0v commented on GitHub (Oct 25, 2024):

Hello Arthur,
Thank you for your attention to this problem.
As I reported the problem appears whenever I create a connection cable between console/power ports.
The problem appeared some time ago after updating the netbox version from 3.6.6 to 4.0.2
To show how the problem shows itself, a screenshot of a newly created server is here
image
No ports have been connected yet.
Now, I'm going to connect the PWR1 port to a power supply.
image
The port is connected to PDU1 and gets status 'Connected'
image
After I press the 'Create' button I see that the connection is in place (it is correctly shown in the 'Connection' column).
The row should have been highlighted in green. However, in my case the line is not highlighted in any way.
In addition the toggle button ('Mark Installed' / 'Mark Planned') is blue and when I hover my mouse over this button, a tooltip 'Mark Installed' pops up, i.e. like the just created connection is treated as a *planned *connection but not installed.
image
When I press the toggle, everything falls into place. The row is highlighted in green, the toggle turns orange and a tooltip 'Mark Planned' appears when I hover my mouse over.
image
From this moment on, when you click on the toggle again and again, everything is displayed correctly and every next click on the toggle changes cable status so that 'planned' connection turns to 'installed' and v.v., and the row is highlighted in a such manner that it turn green for 'installed' connections and blue for 'planned' connections. In other words this really meets expectations on how the toggle color and assigned action to the toggle, the port row color and the cable status depends on each other.
Thus, next click on the toggle gives this -
image
...next click gives this -
image
..and so on.
Everything looks fine until the browser screen is refreshed or this page is reopened. After that, the port is shown exactly as it did immediately after creation, and the same problem appears again. So, if you refresh the screen it will look like on the pic below
image

@Pesk0v commented on GitHub (Oct 25, 2024): Hello Arthur, Thank you for your attention to this problem. As I reported the problem appears whenever I create a connection cable between console/power ports. The problem appeared some time ago after updating the netbox version from 3.6.6 to 4.0.2 To show how the problem shows itself, a screenshot of a newly created server is here ![image](https://github.com/user-attachments/assets/c15d0b22-9c75-4bb7-982e-0a2aadbd99d0) No ports have been connected yet. Now, I'm going to connect the PWR1 port to a power supply. ![image](https://github.com/user-attachments/assets/68a26ecc-564a-4695-bbb2-2569ea81e7dd) The port is connected to PDU1 and gets status 'Connected' ![image](https://github.com/user-attachments/assets/f1215ccf-5e2b-4c9e-bd2d-68127a2dd83c) After I press the 'Create' button I see that the connection is in place (it is correctly shown in the 'Connection' column). The row should have been highlighted in green. However, in my case the line is not highlighted in any way. In addition the toggle button ('Mark Installed' / 'Mark Planned') is blue and when I hover my mouse over this button, a tooltip 'Mark Installed' pops up, i.e. like the just created connection is treated as a *planned *connection but not *installed*. ![image](https://github.com/user-attachments/assets/1d0715e1-4822-454c-a49c-d401ee19f591) When I press the toggle, everything falls into place. The row is highlighted in green, the toggle turns orange and a tooltip 'Mark Planned' appears when I hover my mouse over. ![image](https://github.com/user-attachments/assets/623a67a1-87df-4c74-88ab-e62954fd8c5b) From this moment on, when you click on the toggle again and again, everything is displayed correctly and every next click on the toggle changes cable status so that 'planned' connection turns to 'installed' and v.v., and the row is highlighted in a such manner that it turn green for 'installed' connections and blue for 'planned' connections. In other words this really meets expectations on how the toggle color and assigned action to the toggle, the port row color and the cable status depends on each other. Thus, next click on the toggle gives this - ![image](https://github.com/user-attachments/assets/b4b2418f-5ff4-4423-a0ea-8a2046e1cb21) ...next click gives this - ![image](https://github.com/user-attachments/assets/3cfeae45-4218-48d6-9564-1a01453eea29) ..and so on. Everything looks fine until the browser screen is refreshed or this page is reopened. After that, the port is shown exactly as it did immediately after creation, and the same problem appears again. So, if you refresh the screen it will look like on the pic below ![image](https://github.com/user-attachments/assets/4625c443-bb55-4478-b042-d42bddb070ce)
adam commented 2025-12-29 21:30:59 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Nov 9, 2024):

This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.

@github-actions[bot] commented on GitHub (Nov 9, 2024): This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.
adam commented 2025-12-29 21:30:59 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Nov 16, 2024):

This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.

@github-actions[bot] commented on GitHub (Nov 16, 2024): This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.
adam commented 2025-12-29 21:31:00 +01:00
Author
Owner
Copy Link

@Pesk0v commented on GitHub (Nov 19, 2024):

The problem disappeared right after Netbox had been updated to version v4.1.6 (2024-10-31)

@Pesk0v commented on GitHub (Nov 19, 2024): The problem disappeared right after Netbox had been updated to version v4.1.6 (2024-10-31)
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 netbox pending closure status: revisions needed 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#10399
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?