Bugged metal volumes
alex73630
PROOP

7 months ago

I have an issue with one of my project where some volumes are not showing any metrics.

I believe it's a bug from migrating very early on metal with volumes which also breaks backups (see attached screenshot)

"Luckily", it only impacts our DB which runs as a cluster so we can take each node out one by one to fix them if required.
There's also a Redis instance impacted but the persisted data isn't important (mostly used as rate limit currently)

I've noticed it due to very weird DB cost breakdowns on Volume

Project ID: 1ad2e8d9-d8df-4cd2-aca2-4be43f7219d3

6 Replies

brody
EMPLOYEE

7 months ago

Hello,

These volume types were created when you joined a beta, and we no longer support those volume types.

You would want to deploy a new Postgres database and move your data over manually.


alex73630
PROOP

7 months ago

Got it 👍
I'll plan on migrating them soon then, thanks!


alex73630
PROOP

7 months ago

@Brody ticket can be closed


brody
EMPLOYEE

7 months ago

Thank you for being so understanding, sorry for dropping this on you


alex73630
PROOP

7 months ago

No worries, I expected that jumping early may have consequences so it's ok, I've planned backups for that reason 😄


brody
EMPLOYEE

7 months ago

That is the nature of beta, still not an ideal outcome though.

But I shall mark this as solved!


Loading...