starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-12 05:20:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

VM Status bug #2074

New Issue
Closed
opened 2025-12-29 17:22:02 +01:00 by adam · 0 comments
adam commented 2025-12-29 17:22:02 +01:00
Owner
Copy Link

Originally created by @FedorArbuzov on GitHub (Oct 22, 2018).

Hello! I recently started using api netbox and as it seems to me I found an error in the post method /virtualization/virtual-machines/.

Here api request and response:
url: api/virtualization/virtual-machines/
request body: { "name": "vm-3", "cluster": 1, "status" 2}

answer:
500 error

We have 500 error at the output, but it seems that the insertion into the database still happens. Because after this, all the get requests fall with a 500 error (KeyError: 2). I did a little analysis and found out that in the constant VM_STATUS_ CLASS you have a dictionary {0: 'warning', 1: 'success', 3: 'primary'}. It seems to me that this is the whole point.

Environment

Python version: 3.5.4
NetBox version: 2.4.3

Originally created by @FedorArbuzov on GitHub (Oct 22, 2018). Hello! I recently started using api netbox and as it seems to me I found an error in the post method /virtualization/virtual-machines/. Here api request and response: url: api/virtualization/virtual-machines/ request body: { "name": "vm-3", "cluster": 1, "status" 2} answer: 500 error We have 500 error at the output, but it seems that the insertion into the database still happens. Because after this, all the get requests fall with a 500 error (KeyError: 2). I did a little analysis and found out that in the constant VM_STATUS_ CLASS you have a dictionary {0: 'warning', 1: 'success', 3: 'primary'}. It seems to me that this is the whole point. Environment Python version: 3.5.4 NetBox version: 2.4.3
adam closed this issue 2025-12-29 17:22:03 +01:00
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
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#2074
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?