Open afaianswq opened 6 months ago
This seems like some code that was written a while ago that does not directly influence the import process. Are you importing into a clean install of sentry? Is there information in your db?
cc @azaslavsky
Is this error repeatable? I think it's a racy interaction of post-delete signals, and would work on the following try.
Yes, it's 100% reproducible.
This seems like some code that was written a while ago that does not directly influence the import process. Are you importing into a clean install of sentry? Is there information in your db?
cc @azaslavsky
I am importing into the same instance, so yes, there is information in the db.
I have just tested it with version 24.5.0 and the issue reproduced.
Are you also exporting from version 24.5.0? It's important to note that we only support imports from versions that are 3 versions from the version you're importing into. So, in your case, it would be 24.3.0
Yes, export/import is attempted on the same version always.
You may need to drop this table manually. Is your instance currently working (ie, you failed to load the backup, but the instance still works as before)? Or is it completely bricked (which is what I would expect from this stack trace).
In any case, you'll need to use psql to drop the offending table manually - but please do a full backup first!
Which table do I need to drop? And why? I am not looking for a quick workaround. I want backup/restore feature to work reliably.
I think I have a solution for this, will try to get it up by Monday.
Update: it's a bit more involved than I had anticipated, so it may take a few days to get to the bottom of this and resolve. But I do believe this is fundamentally a bug on our end.
Hello. Any news on this?
Got a bit derailed by some other work, hoping to pick this up next week.
Bump...
Another bump. Can someone please address this quite critical issue?
Bump
Bump
Please keep in mind that this issue is on our radar, we just haven't gotten to it yet. Please avoid bumping this as it is not helpful to us for prioritization.
Why is it still on your radar after 3 months? Restoring from a backup is a essential and critical part of the product, this bug is supposed to have critical priority.
Any progress? This bug is holding us from upgrading from a more than one year old version.
No progress at the moment.
cc @azaslavsky
Self-Hosted Version
23.12.1
CPU Architecture
x86_64
Docker Version
26.1.3
Docker Compose Version
2.27.0
Steps to Reproduce
cd /path/to/sentry-dist/sentry
docker compose run --rm -T web export global > backup.json
docker compose run --rm -T web import global --no-prompt /etc/sentry/backup.json
Expected Result
Backup imported without issues
Actual Result
Restore fails with the following exception:
Event ID
No response