Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Bug: Migration from v4.13 to v5.x doesn't work #3241

Open
Metal-Mighty opened this issue Oct 16, 2024 · 0 comments
Open

Bug: Migration from v4.13 to v5.x doesn't work #3241

Metal-Mighty opened this issue Oct 16, 2024 · 0 comments
Assignees
@judramos
Labels
bug Something isn't working component: database
Milestone
v6.0

Comments

@Metal-Mighty
Copy link
Contributor

Expected Behavior

Migration should apply changes required to move from an existing v4.13 database to a v5.x database

Current Behavior

Migrations are applied but the portal doesn't work properly when it's done

Steps to Reproduce

  1. Install the portal in v4.13
  2. Insert data in models, devices, etc.
  3. Deploy version v5.x connected to the same database

Context (Environment)

Portal version: 4.13 -> 5.x
LoRaWAN Stack version: N/A

Logs

Additional Information
@Metal-Mighty Metal-Mighty added bug Something isn't working component: database labels Oct 16, 2024
@Metal-Mighty Metal-Mighty added this to the v6.0 milestone Oct 16, 2024
@github-project-automation github-project-automation bot moved this to 🔦 Triage in IoT Hub Portal Oct 16, 2024
@judramos judramos self-assigned this Oct 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@judramos judramos

Labels
bug Something isn't working component: database
Projects
IoT Hub Portal
Status: 🚧 In Progress
Milestone
v6.0
Development

No branches or pull requests
2 participants
@Metal-Mighty @judramos