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.

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

Regression: Fix migration 125 checking for settings field #11364

Merged
merged 1 commit into from
Jul 6, 2018

Conversation

sampaiodiego
Copy link
Member

@sampaiodiego sampaiodiego commented Jul 6, 2018

Closes #11353

Unfortunate seems like some databases have settings field on users as null, which causes migration 125 to fail.

This will fix the migration for those who have not ran it yet.

For those who are still locked on migration 125, upgrading to a new release with this fix will require the migration to be unlocked manually only using the following command:

db.migrations.update({ version: 124, locked: true }, { $set: { version: 124, locked: false } })

For those who have skipped migration 125-129 manually, the recommended action is to revert back to version 125 and start the server with this fix. To revert back you can use the following command:

db.migrations.update({ version: 129, locked: false }, { $set: { version: 124 } })

And finally for those still stuck with the migration locked, just updating to latest version/codebase will fix it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

migration failed upgrading from 0.65.2 to 0.66.1
3 participants