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.

Sign up for GitHub

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

Jump to bottom

Updating VM cluster devices fails to generate a changelog. #2368

Closed
ebusto opened this issue Aug 16, 2018 · 0 comments
Closed

Updating VM cluster devices fails to generate a changelog. #2368

ebusto opened this issue Aug 16, 2018 · 0 comments
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@ebusto
Copy link

ebusto commented Aug 16, 2018

Environment

  • Python version: 3.5.4
  • NetBox version: 2.4.3

Steps to Reproduce

Create a VM cluster, then assign a device to the cluster using the web UI.

Expected Behavior

A changelog entry for the device indicating that the cluster field has been updated.

Observed Behavior

No changelog was generated.

I believe this is due to NetBox updating the devices en masse with objects.filter(...).update(...). Unfortunately, there is a Django bug (marked will not fix) that prevents this from sending signals.

The simple fix would be to loop through the devices and update them individually.
@jeremystretch jeremystretch added type: bug A confirmed report of unexpected behavior in the application status: accepted This issue has been accepted for implementation labels Aug 17, 2018
jeremystretch added a commit that referenced this issue Aug 17, 2018
@jeremystretch
#2368: Append changelog
d46b3e2
@jeremystretch jeremystretch mentioned this issue Aug 22, 2018
Merged
@lock lock bot locked as resolved and limited conversation to collaborators Jan 17, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ebusto @jeremystretch