Closed erfansahaf closed 3 years ago
Looks like something is messed up in the GitHub plugin. As a workaround, can you install the plugin before exporting (or expunge it from the export) before importing?
Or if that's not it, can you otherwise whittle down what exactly in your export is causing the error on import? Can you send us a minimal test case to repro the bug?
I deleted the previous project and installed a new fresh Sentry with the latest version (21) so I don't have access to logs/database anymore. All I have is the exported backup file.
Can you bisect the export file to find the offending bit? Whittle it down that way?
@chadwhitacre Since it contains sensitive data (password, etc.) I prefer to share it privately with you, if possible.
Did you figure out which part of the export file is choking the import process? Which is it?
This issue has gone three weeks without activity. In another week, I will close it.
But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog
or Status: In Progress
, I will leave it alone ... forever!
"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀
This should be fixed with getsentry/sentry#24461.
Version Information
Version: 20.10.1
Steps to Reproduce
Take a quick backup on a working sentry instance.
Takedown all the containers. Remove all volumes and try to install the sentry again by running the
./install.sh
script.Restore the taken backup from the first step with the following command:
docker-compose run --rm -T web import /etc/sentry/backup.json
Expected Result
Restore the backup file without any error.
Actual Result
Facing the following error:
Logs
I entered the No answer for creating default user/project prompt in the installation process to keep the database empty with executed migrations.