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

Status tab claims device is inactive #3189

New Issue
Closed
opened 2025-12-29 18:26:28 +01:00 by adam · 1 comment
adam commented 2025-12-29 18:26:28 +01:00
Owner
Copy Link

Originally created by @lukasjuhrich on GitHub (Jan 20, 2020).

Environment

  • Python version: 3.7.6
  • NetBox version: 2.7.1

Steps to Reproduce

  1. Have DCIM devices which are active (in the sense of the dcim_device.status column in the database) and have a valid database navigation
  2. Navigate to the device overview

Expected Behavior

The status tab should be enabled and clickable.

Observed Behavior

The status tab is not clickable, instead it reports device must be in active status.
However, manually navigating to status/ works perfectly fine and displays all desired data.

Probable reason

The template still checks device.status == 1 using the legacy numerical value (although this might be plain wrong because I don't know the codebase).

Originally created by @lukasjuhrich on GitHub (Jan 20, 2020). ### Environment * Python version: 3.7.6 * NetBox version: 2.7.1 ### Steps to Reproduce 1. Have DCIM devices which are `active` (in the sense of the `dcim_device.status` column in the database) and have a valid database navigation 2. Navigate to the device overview <!-- What did you expect to happen? --> ### Expected Behavior The `status` tab should be enabled and clickable. <!-- What happened instead? --> ### Observed Behavior The `status` tab is not clickable, instead it reports `device must be in active status`. However, manually navigating to `status/` works perfectly fine and displays all desired data. ### Probable reason The [template](https://github.com/netbox-community/netbox/blob/v2.7.1/netbox/templates/dcim/device.html#L87) still checks `device.status == 1` using the legacy numerical value (although this might be plain wrong because I don't know the codebase).
adam added the type: bugstatus: accepted labels 2025-12-29 18:26:28 +01:00
adam closed this issue 2025-12-29 18:26:28 +01:00
adam commented 2025-12-29 18:26:29 +01:00
Author
Owner
Copy Link

@kobayashi commented on GitHub (Jan 21, 2020):

Confirmed and accepted this as bug.

@kobayashi commented on GitHub (Jan 21, 2020): Confirmed and accepted this as bug.
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: accepted 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#3189
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?