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

Change Log doesn't update in device view when changing device interfaces #6403

New Issue
Closed
opened 2025-12-29 19:40:17 +01:00 by adam · 4 comments
adam commented 2025-12-29 19:40:17 +01:00
Owner
Copy Link

Originally created by @cs-1 on GitHub (Apr 26, 2022).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.2.1

Python version

3.8

Steps to Reproduce

  1. Make a change to a device's interface.
  2. Open device's Change Log tab.

Expected Behavior

Interface changes show up in the device's Change Log.

Observed Behavior

The new changes to interfaces do not appear in the Change Log tab of a device only changes to interfaces before the beginning of April 2022 show up.

However, the new changes do show up in the Change Log of the main NetBox dashboard and also under "Other / Change Log". From what I can tell this issue exists since migrating from 3.1.x to 3.2.x.

Originally created by @cs-1 on GitHub (Apr 26, 2022). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.2.1 ### Python version 3.8 ### Steps to Reproduce 1. Make a change to a device's interface. 2. Open device's Change Log tab. ### Expected Behavior Interface changes show up in the device's Change Log. ### Observed Behavior The new changes to interfaces do not appear in the Change Log tab of a device only changes to interfaces before the beginning of April 2022 show up. However, the new changes do show up in the Change Log of the main NetBox dashboard and also under "Other / Change Log". From what I can tell this issue exists since migrating from 3.1.x to 3.2.x.
adam added the type: bugstatus: accepted labels 2025-12-29 19:40:17 +01:00
adam closed this issue 2025-12-29 19:40:17 +01:00
adam commented 2025-12-29 19:40:18 +01:00
Author
Owner
Copy Link

@hagbarddenstore commented on GitHub (Apr 26, 2022):

Interfaces are its own model, so they show up on the Changelog for that model. In the Interfaces list, select an interface and it will have the changelog tab in the details view.

Sent from my iPhone

On 26 Apr 2022, at 16:06, cs-1 @.***> wrote:


NetBox version

v3.2.1

Python version

3.8

Steps to Reproduce

Make a change to a device's interface.
Open device's Change Log tab.
Expected Behavior

Interface changes show up in the device's Change Log.

Observed Behavior

The new changes to interfaces do not appear in the Change Log tab of a device only changes to interfaces before the beginning of April 2022 show up.

However, the new changes do show up in the Change Log of the main NetBox dashboard and also under "Other / Change Log". From what I can tell this issue exists since migrating from 3.1.x to 3.2.x.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

@hagbarddenstore commented on GitHub (Apr 26, 2022): Interfaces are its own model, so they show up on the Changelog for that model. In the Interfaces list, select an interface and it will have the changelog tab in the details view. Sent from my iPhone > On 26 Apr 2022, at 16:06, cs-1 ***@***.***> wrote: > >  > NetBox version > > v3.2.1 > > Python version > > 3.8 > > Steps to Reproduce > > Make a change to a device's interface. > Open device's Change Log tab. > Expected Behavior > > Interface changes show up in the device's Change Log. > > Observed Behavior > > The new changes to interfaces do not appear in the Change Log tab of a device only changes to interfaces before the beginning of April 2022 show up. > > However, the new changes do show up in the Change Log of the main NetBox dashboard and also under "Other / Change Log". From what I can tell this issue exists since migrating from 3.1.x to 3.2.x. > > — > Reply to this email directly, view it on GitHub, or unsubscribe. > You are receiving this because you are subscribed to this thread.
adam commented 2025-12-29 19:40:18 +01:00
Author
Owner
Copy Link

@cs-1 commented on GitHub (Apr 27, 2022):

While that's true, that is not the way it used to work in 3.1.x. We even still have changes for interfaces in the device's Change Log tab that were made before the upgrade to 3.2.x. From a pure usability point of view it makes perfect sense that changing a device's interface is a change made to the device. Unless I've missed something, there're no hints in the changelog of NetBox that the functionality of a device's Change Log has been changed. That's why I think that this change in behaviour is unintentional.

@cs-1 commented on GitHub (Apr 27, 2022): While that's true, that is not the way it used to work in 3.1.x. We even still have changes for interfaces in the device's Change Log tab that were made before the upgrade to 3.2.x. From a pure usability point of view it makes perfect sense that changing a device's interface is a change made to the device. Unless I've missed something, there're no hints in the changelog of NetBox that the functionality of a device's Change Log has been changed. That's why I think that this change in behaviour is unintentional.
adam commented 2025-12-29 19:40:19 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 27, 2022):

There's a bug in the to_objectchange() method on the Interface model that's bypassing the assignment of the parent device as a related object. Interface seems to be the only model affected.

@jeremystretch commented on GitHub (Apr 27, 2022): There's a bug in the `to_objectchange()` method on the Interface model that's bypassing the assignment of the parent device as a related object. Interface seems to be the only model affected.
adam commented 2025-12-29 19:40:19 +01:00
Author
Owner
Copy Link

@cs-1 commented on GitHub (Apr 28, 2022):

Hi Jeremy!

Thanks for the quick fix. Your help and the effort you put into NetBox is highly appreciated!

@cs-1 commented on GitHub (Apr 28, 2022): Hi Jeremy! Thanks for the quick fix. Your help and the effort you put into NetBox is highly appreciated!
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#6403
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?