Hi folks, I have some failing migration on the lat...
# fleet
c
Hi folks, I have some failing migration on the latest update. Deployed via K8s on GCP:
Copy code
################################################################################
# WARNING:
#   This will perform Fleet database migrations. Please back up your data before
#   continuing.
#
#   Missing migrations: tables=[20240826160025 20240829165448 20240829165605 20240829165715 20240829165930 20240829170023 20240829170033 20240829170044 20240905105135 20240905140514 20240905200000 20240905200001 20241002104104], data=[].
#
#   Press Enter to continue, or Control-c to exit.
################################################################################
2024/10/14 23:14:10 [2024-08-26] Add Removed To Installs
2024/10/14 23:14:10 FAIL 20240826160025_AddRemovedToInstalls.go (failed to find host_software_installs to remove: Error 1054 (42S22): Unknown column 'st.id' in 'on clause'), quitting migration.
Any recommendations?
I was able to work around this by taking
fleet prepare db
out of my launch command, but I assume I'm hitting this error because I have these settings disabled:
Copy code
features:
    enable_host_users: true
    enable_software_inventory: false
z
hey @clong which version were you upgrading from and which version were you upgrading to?
c
Upgrading to
4.57.3
. Looks like I had things pinned to latest (😬 ) so upgrading from whatever version was previous to this
@Zay Hanlon sorry, just wanted to check to see if you had any guidance of how i could resolve this migration issue -- happy to open a GH issue for tracking if that's better
z
@clong - let's see if my team can jump in and help before we kick off an issue for you. @Rebecca Cowart or @Kathy Satterlee can you take a look here? ^
k
What version of MySQL are you running? The minimum required version is v8.0.36 and I've seen this error pop up for previous versions of MySQL.
c
looks like 5.7
let me look at my options for upgrading 👀
OK, attempting the upgrade now 🙏
Migrations completed.
🎉
z
Beautiful! Sorry I should’ve suggested this last night @clong
c
might be worth having a check in that migration for the SQL version and to post an error like "if you're hitting this error, ensure you're running SQL version v8.0.36+"
but glad we're back in action 🙂
k
Great feedback @clong, glad you're up and running!