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

Cable status schema migration is broken #3141

New Issue
Closed
opened 2025-12-29 18:26:04 +01:00 by adam · 0 comments
adam commented 2025-12-29 18:26:04 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Jan 9, 2020).

Environment

  • Python version: 3.6.8
  • NetBox version: 2.7-beta1

Steps to Reproduce

  1. Migrate a v2.6 database to v2.7-beta1
  2. View the cables list

Expected Behavior

The legacy status BooleanField is migrated to a CharField as part of the upgrade. True should be replaced with connected and False should be replaced with planned.

Observed Behavior

The status field is retaining the string form of its previous boolean value (e.g. true or false). The first six cables in the example below have had their statuses corrected manually via the NetBox UI:

netbox=> select id, status from dcim_cable order by id limit 10;
 id |  status   
----+-----------
  1 | planned
  2 | planned
  3 | planned
  4 | connected
  5 | connected
  6 | connected
  7 | true
  8 | true
  9 | true
 10 | true
Originally created by @jeremystretch on GitHub (Jan 9, 2020). ### Environment * Python version: 3.6.8 * NetBox version: 2.7-beta1 ### Steps to Reproduce 1. Migrate a v2.6 database to v2.7-beta1 2. View the cables list ### Expected Behavior The legacy `status` BooleanField is migrated to a CharField as part of the upgrade. `True` should be replaced with `connected` and `False` should be replaced with `planned`. ### Observed Behavior The status field is retaining the string form of its previous boolean value (e.g. `true` or `false`). The first six cables in the example below have had their statuses corrected manually via the NetBox UI: ``` netbox=> select id, status from dcim_cable order by id limit 10; id | status ----+----------- 1 | planned 2 | planned 3 | planned 4 | connected 5 | connected 6 | connected 7 | true 8 | true 9 | true 10 | true ```
adam added the type: bugstatus: accepted labels 2025-12-29 18:26:04 +01:00
adam closed this issue 2025-12-29 18:26:04 +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 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#3141
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?