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

Custom field defaults are not set on templated device/VM components upon creation #14322

Closed
jwbensley opened this issue Nov 22, 2023 · 1 comment · Fixed by #14443
Closed

Custom field defaults are not set on templated device/VM components upon creation #14322

jwbensley opened this issue Nov 22, 2023 · 1 comment · Fixed by #14443
Assignees
@jeremystretch
Labels
severity: medium Results in substantial degraded or broken functionality for specfic workflows status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@jwbensley
Copy link

NetBox version

v3.5.9

Python version

3.10

Steps to Reproduce

  • Create a custom field which is required AND has a default value. In this example we have a boolean field which is required and has a default value of False:

grafik

  • Now I create a new device in NetBox based off of an existing device template. We can see it has a bunch of interfaces already defined:

grafik

  • If I examine the interfaces, they all have no value set for this custom field, even though a default is defined:

grafik

  • Each time we create a device, we have to set this value for all the interfaces, every though a default has been defined. This is why I think this is a bug, the default value is not being set.

Expected Behavior

All these interfaces should have this custom field set to False by default as per the custom field definition.

Observed Behavior

All instances of this custom field have no value set which I think is unexpected when you consider that this is a required boolean field, and neither True nor False is set.
@jwbensley jwbensley added the type: bug A confirmed report of unexpected behavior in the application label Nov 22, 2023
@jeremystretch jeremystretch changed the title Custom field default isn't being set Custom field defaults are not set on templated device/VM components upon creation Nov 22, 2023
@jeremystretch jeremystretch added the status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation label Nov 22, 2023
@jeremystretch jeremystretch added the severity: medium Results in substantial degraded or broken functionality for specfic workflows label Dec 5, 2023
@jeremystretch jeremystretch self-assigned this Dec 5, 2023
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation and removed status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation labels Dec 5, 2023
jeremystretch added a commit that referenced this issue Dec 5, 2023
@jeremystretch
Fixes #14322: Populate default custom field values when instantiating…
d542621 
… templated device components
@jeremystretch jeremystretch mentioned this issue Dec 5, 2023
Merged
jeremystretch added a commit that referenced this issue Dec 6, 2023
@jeremystretch
Fixes #14322: Populate default custom field values when instantiating…
32264ac 
… templated device components
@jwbensley
Copy link
Author

Thanks for the quick fix!

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 13, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jeremystretch jeremystretch

Labels
severity: medium Results in substantial degraded or broken functionality for specfic workflows 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
2 participants
@jwbensley @jeremystretch