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

Additional status value on Device/Virtual Machine #5604

New Issue
Closed
opened 2025-12-29 19:30:04 +01:00 by adam · 9 comments
adam commented 2025-12-29 19:30:04 +01:00
Owner
Copy Link

Originally created by @ziggekatten on GitHub (Nov 3, 2021).

NetBox version

v3.0.8

Feature type

New functionality

Proposed functionality

Devices and Virtual machines have various statuses. Currently there is one called Decomissioning which makes sense during the work to decomission. What is missing is an status called Decomissioned, in effect when done, this status would be used on the device/vm.

Use case

We would like to keep journal entries for dekomissioned objects some time, and deleting a device/vm deletes Journal entries. To be able to distinguish if a object are under decomissioning or if it is actually done, an additional Status would be good.

Database changes

none

External dependencies

none

Originally created by @ziggekatten on GitHub (Nov 3, 2021). ### NetBox version v3.0.8 ### Feature type New functionality ### Proposed functionality Devices and Virtual machines have various statuses. Currently there is one called Decomissioning which makes sense during the work to decomission. What is missing is an status called Decomissioned, in effect when done, this status would be used on the device/vm. ### Use case We would like to keep journal entries for dekomissioned objects some time, and deleting a device/vm deletes Journal entries. To be able to distinguish if a object are under decomissioning or if it is actually done, an additional Status would be good. ### Database changes none ### External dependencies none
adam added the type: feature label 2025-12-29 19:30:04 +01:00
adam closed this issue 2025-12-29 19:30:04 +01:00
adam commented 2025-12-29 19:30:04 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 5, 2021):

Both the device and virtual machine models already offer an "offline" status choice. Does this not meet your criteria above?

@jeremystretch commented on GitHub (Nov 5, 2021): Both the device and virtual machine models already offer an "offline" status choice. Does this not meet your criteria above?
adam commented 2025-12-29 19:30:04 +01:00
Author
Owner
Copy Link

@ziggekatten commented on GitHub (Nov 5, 2021):

Not really, as we use that for powered off machines (one example root CA servers) etc.

@ziggekatten commented on GitHub (Nov 5, 2021): Not really, as we use that for powered off machines (one example root CA servers) etc.
adam commented 2025-12-29 19:30:05 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Nov 5, 2021):

Related: #2394 #5180 #3401 #2045

(Hope this is all of them)

@DanSheps commented on GitHub (Nov 5, 2021): Related: #2394 #5180 #3401 #2045 (Hope this is all of them)
adam commented 2025-12-29 19:30:05 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Nov 5, 2021):

I think if you are not removing it from netbox, it should honestly go back to "Inventory" state.

@DanSheps commented on GitHub (Nov 5, 2021): I think if you are not removing it from netbox, it should honestly go back to "Inventory" state.
adam commented 2025-12-29 19:30:05 +01:00
Author
Owner
Copy Link

@ziggekatten commented on GitHub (Nov 5, 2021):

Well, inventory makes sense when you have a device/vm actually in existence, but yet not fully active. Example, switch arrived mounted, but yet not active in a sense that it takes traffic. In this state, we add the object to our CMDB.

Now, since we already have a staus Decomissioning in netbox that by name define a intermediate state, it would in my view make sense to have a final status after decomissioning is done. Tags are great for many things, but clutter objects with tags just in specific cases, when a status field already exists seems ankward.

Another thing to consider is when looking at Netbox data from the outside (dashboards/analytics), mixing fields with tags to represent the state causes unnecessary logic.

Issue might seem trivial, but as a source of truth, it also feeds ecosystems outside the bare infra world.

@ziggekatten commented on GitHub (Nov 5, 2021): Well, inventory makes sense when you have a device/vm actually in existence, but yet not fully active. Example, switch arrived mounted, but yet not active in a sense that it takes traffic. In this state, we add the object to our CMDB. Now, since we already have a staus Decomissioning in netbox that by name define a intermediate state, it would in my view make sense to have a final status after decomissioning is done. Tags are great for many things, but clutter objects with tags just in specific cases, when a status field already exists seems ankward. Another thing to consider is when looking at Netbox data from the outside (dashboards/analytics), mixing fields with tags to represent the state causes unnecessary logic. Issue might seem trivial, but as a source of truth, it also feeds ecosystems outside the bare infra world.
adam commented 2025-12-29 19:30:05 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Nov 8, 2021):

What happens when you decommission the device? Does it get disposed of? Can it be reused?

@DanSheps commented on GitHub (Nov 8, 2021): What happens when you decommission the device? Does it get disposed of? Can it be reused?
adam commented 2025-12-29 19:30:05 +01:00
Author
Owner
Copy Link

@ziggekatten commented on GitHub (Nov 9, 2021):

Some devices get reused, and are set to status inventory if just on the shelf, and Active if used again.

But if they are scrapped, we would like to have status Decomissioned, thus keeping journal entries (for one year), and after that, delete them.

@ziggekatten commented on GitHub (Nov 9, 2021): Some devices get reused, and are set to status inventory if just on the shelf, and Active if used again. But if they are scrapped, we would like to have status Decomissioned, thus keeping journal entries (for one year), and after that, delete them.
adam commented 2025-12-29 19:30:05 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 13, 2021):

Marking this as blocked by #8054. (If implemented, this issue will become moot.)

@jeremystretch commented on GitHub (Dec 13, 2021): Marking this as blocked by #8054. (If implemented, this issue will become moot.)
adam commented 2025-12-29 19:30:06 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 22, 2021):

#8054 has been implemented and the ability to define custom status choices will be available in NetBox v3.2.

@jeremystretch commented on GitHub (Dec 22, 2021): #8054 has been implemented and the ability to define custom status choices will be available in NetBox v3.2.
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 type: feature
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#5604
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?