Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Front Ports count is not updated when removing rear ports. #14323

Closed
Chiniquy opened this issue Nov 22, 2023 · 2 comments
Closed

Front Ports count is not updated when removing rear ports. #14323

Chiniquy opened this issue Nov 22, 2023 · 2 comments
Labels
status: duplicate This issue has already been raised type: bug A confirmed report of unexpected behavior in the application

Comments

@Chiniquy
Copy link

NetBox version

v3.6.5

Python version

3.8

Steps to Reproduce

Create a device (preferably of a device type without any front or rear ports).
On this device, create a rear port with name "test" and type "Other", with 2 positions.
Create 2 frontports by using "test [1-2]" as name, with type "Other", and select the 2 positions of the newly created rear port.
Now remove the rear port that you created.
On the device view you will now see a "2" on the Front port tab, but there will be no Front Ports inside the tab.

Expected Behavior

If the Front Ports are deleted, then the "2" on the Front Port tab should not be there, and the tab should not be visible.

Observed Behavior

The Front Port tab shows the number "2", indicating the existance of 2 Front Ports. However, when clicking on the Front Port tab, no Front Ports are visible.

@Chiniquy Chiniquy added the type: bug A confirmed report of unexpected behavior in the application label Nov 22, 2023
@jeremystretch jeremystretch added status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation severity: medium Results in substantial degraded or broken functionality for specfic workflows labels Nov 28, 2023
@jeremystretch
Copy link
Member

It seems that the cascading deletion triggered by removing the rear port is not detected by the tracking logic.

@jeremystretch
Copy link
Member

I believe this is the same root problem covered by #14081, so I'm going to close this out as a duplicate (even though its focus is on a different symptom). Happy to reopen it if we see that the fix for #14081 does not resolve this.

@jeremystretch jeremystretch closed this as not planned Won't fix, can't repro, duplicate, stale Nov 29, 2023
@jeremystretch jeremystretch added status: duplicate This issue has already been raised and removed status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation severity: medium Results in substantial degraded or broken functionality for specfic workflows labels Nov 29, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 28, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: duplicate This issue has already been raised type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

2 participants