Comment 2 for bug 1699515

So this is due to a bad cherry-pick. DB migrations can't be cherry-picked out of order, or they will mess with upgrades. What happens in this case, is that the DB is already at version 20 in newton (Increase environments_v2 column size from JsonDictType to JsonLongDictType), then ocata comes along and replaces that with 'add type to task execution' as migration 20, and makes the 'Increate environments_v2' migration number 21. So, it only applies that again, without actually applying the 'add type to task execution' migration.