self-hosted Nodestore migration interrupted, how to resume?

Self-Hosted Version

25.11.1

CPU Architecture

x86_64

Docker Version

28.0.1

Docker Compose Version

2.33.1

Machine Specification

[x] My system meets the minimum system requirements of Sentry

Installation Type

Upgrade from 25.9 to 25.11.1

Steps to Reproduce

My ssh connection dropped during the nodestore migration. When I try running install.sh again, I get "ERROR: Bucket 'nodestore' already exists ... Error in install/bootstrap-s3-nodestore.sh:64

Is there a way to resume this? If I just change the shell script to not fail on that error, will it resume properly? Or is there another solution?

Thank you!

Expected Result

Running install.sh resumes the nodestore migration.

Actual Result

"ERROR: Bucket 'nodestore' already exists ... Error in install/bootstrap-s3-nodestore.sh:64

Event ID

No response

Dec 09 '25 14:12 thinkspill

Looks like this is fixed by this commit? https://github.com/getsentry/self-hosted/commit/ebace8c6628c0ecedbccdf996aad65982bcfe7d8

Dec 09 '25 18:12 zach-prometheus

Will this workaround safely resume the migration?

Dec 09 '25 18:12 thinkspill

I performed the workaround and re-ran install.sh. I see the text stating the profiles bucket exists and was skipping creation, and the rest of the script completed, but it doesn't seem like any further file migration happened. I don't know if this is important or not, or what functionality might be impacted.

Dec 09 '25 19:12 thinkspill

I don't know if this is important or not, or what functionality might be impacted.

The impact is only the profiling data, but if you don't use it as much, then it's not really important.

Anyway, 25.12.0 is out, please consider upgrading :D

Dec 17 '25 00:12 aldy505