19913d85-f662-4518-a9a1-7adc1793dfd4.png){kind=small}
Hi team, for migrating dagit & daemon from 0.1...
# ask-communityh
Hebo Yang
08/03/2022, 5:05 AMHi team, for migrating dagit & daemon from 0.14 to 0.15, it’s not mentioned here to run
dagster instance migrate🤖 1
Hebo Yang
08/03/2022, 5:13 AM(context: our helm & k8s deployment are managed systematically and it’s significant overhead for us to do
dagster instance migrateHebo Yang
08/03/2022, 5:25 PMcc @claire and @daniel who helped with our migration before:)
c
claire
08/03/2022, 5:32 PMHi Hebo. Yes that's right--you do not have to run
dagster instance migrateh
Hebo Yang
08/03/2022, 5:49 PMThanks Claire!! This is AWESOME!! We could just go from 0.14.5 to 0.15.6 directly by updating the version in Helm chart? (We use Helm K8s deployment)
c
claire
08/03/2022, 5:56 PMHmm... in 0.14.8 we fixed a bug where schedules/sensors got out of sync between Dagit and Dagster-daemon. If you're running into this bug, you may have to run
dagster instance migrateclaire
08/03/2022, 5:57 PMBut if you're not running into this bug, you don't have to run the migration.
h
Hebo Yang
08/03/2022, 6:00 PMI see. We didn’t run into the problem that schedules / sensors getting marked as “Unloadable” in Dagit. However, we have seen instances where disabled sensors auto turn themselves on again. Is it the same issue that needs to run migration please?
c
claire
08/03/2022, 6:02 PMI'm not sure, asking the team now
claire
08/03/2022, 6:09 PMNope--this issue does not require migration. The issue where sensors auto turn themselves on is resolved in 0.14.15
celebrate 1
h
Hebo Yang
08/03/2022, 6:16 PMGreat! Thanks again Claire! This is awesome!
🌈 1
3 Views