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

Unknown field name '1' in custom field data. #5457

New Issue
Closed
opened 2025-12-29 19:28:16 +01:00 by adam · 3 comments
adam commented 2025-12-29 19:28:16 +01:00
Owner
Copy Link

Originally created by @xsgb on GitHub (Oct 1, 2021).

NetBox version

v3.0.4

Python version

3.8

Steps to Reproduce

  • Edit a virtual machine ( I change the status value )
  • Send the form with Apply

Note: I had this issue on v2.9, I tought migrating to 3 might help but there's the same problem. We have about 15 custom fields for VM's. No one is called '1'.

Expected Behavior

Value updated in the DB and no error.

Observed Behavior

  • See this error: Unknown field name '1' in custom field data.
  • Entry is not updated

Here's a debug log when I click on Apply", there's suspicious things
debug.log.a.txt

Originally created by @xsgb on GitHub (Oct 1, 2021). ### NetBox version v3.0.4 ### Python version 3.8 ### Steps to Reproduce - Edit a virtual machine ( I change the status value ) - Send the form with Apply Note: I had this issue on v2.9, I tought migrating to 3 might help but there's the same problem. We have about 15 custom fields for VM's. No one is called '1'. ### Expected Behavior Value updated in the DB and no error. ### Observed Behavior - See this error: Unknown field name '1' in custom field data. - Entry is not updated Here's a debug log when I click on Apply", there's suspicious things [debug.log.a.txt](https://github.com/netbox-community/netbox/files/7268632/debug.log.a.txt)
adam added the type: bugstatus: revisions needed labels 2025-12-29 19:28:16 +01:00
adam closed this issue 2025-12-29 19:28:16 +01:00
adam commented 2025-12-29 19:28:17 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 1, 2021):

Thank you for opening a bug report. 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.

@jeremystretch commented on GitHub (Oct 1, 2021): Thank you for opening a bug report. 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.
adam commented 2025-12-29 19:28:17 +01:00
Author
Owner
Copy Link

@xsgb commented on GitHub (Oct 4, 2021):

Hi,

I greatly appreciate and totally understand your answer. This will take a little time for my team to investigate and provide further information by re-deploying another separated Netbox instance and perform our virtual machine synchronization done by https://github.com/bb-Ricardo/netbox-sync to fill VM data.

Maybe this script I just cited is responsible responsible but I'm not sure how it could alter the custom_fields structure.

I'll append a comment once those information are ready. It's not yet our top priority. Don't mind a 2/3 days lag from our side.

Have a great day!

@xsgb commented on GitHub (Oct 4, 2021): Hi, I greatly appreciate and totally understand your answer. This will take a little time for my team to investigate and provide further information by **re-deploying another separated Netbox instance** and perform our virtual machine synchronization done by https://github.com/bb-Ricardo/netbox-sync to fill VM data. Maybe this script I just cited is responsible responsible but I'm not sure how it could alter the _custom_fields_ structure. I'll append a comment once those information are ready. It's not yet our top priority. Don't mind a 2/3 days lag from our side. Have a great day!
adam commented 2025-12-29 19:28:17 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 4, 2021):

and perform our virtual machine synchronization done by https://github.com/bb-Ricardo/netbox-sync to fill VM data.

Please bear in mind that we cannot accept bug reports for anything that involves code outside of core NetBox project. Any reported bugs must be fully reproducible without any installed plugins or other ancillary code.

I'm going to close this for now as the required information is not available, but if you are able to reproduce the reported behavior using a stock NetBox installation, please comment again and I'll re-open it.

@jeremystretch commented on GitHub (Oct 4, 2021): > and perform our virtual machine synchronization done by https://github.com/bb-Ricardo/netbox-sync to fill VM data. Please bear in mind that we cannot accept bug reports for anything that involves code outside of core NetBox project. Any reported bugs must be fully reproducible without any installed plugins or other ancillary code. I'm going to close this for now as the required information is not available, but if you are able to reproduce the reported behavior using a stock NetBox installation, please comment again and I'll re-open it.
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: 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#5457
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?