Skip to content

Cable status schema migration is broken #3878

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
jeremystretch opened this issue Jan 9, 2020 · 0 comments
Closed

Cable status schema migration is broken #3878

jeremystretch opened this issue Jan 9, 2020 · 0 comments
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@jeremystretch
Copy link
Member

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
@jeremystretch jeremystretch added type: bug A confirmed report of unexpected behavior in the application status: accepted This issue has been accepted for implementation beta labels Jan 9, 2020
@lock lock bot locked as resolved and limited conversation to collaborators Apr 15, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

1 participant