Error on storage downsized whereas db never deployed

[clemg (Clem)]

ISSUE

Cannot set a specific storage size after cloning env.

HOW TO REPRODUCE

1. Clone env
2. Update storage size (managed Postgres database)
3. Save → error

[bchastanier (Benjamin Chastanier)]

Hello @clemg,

Thanks for reporting, one question: did you try to update the size storage before to deploy the cloned env or after?

Thanks

[bchastanier (Benjamin Chastanier)]

Hello @clemg,

We do not allow to downscale a DB / app volume if the service has already be running once since it can lead to bigger issues such as data loss or unrecoverable errors.

In the case of DBs, as you seem to have faced, we do not allow the downscale even for not running service (just cloned for example).
I made a patch for this in order to allow it as we do for applications.

Fix should land anytime today, I will keep you posted here once done.

Cheers

[clemg (Clem)]

Hi @bchastanier,

I had this error before deploying the db the first time (so there shouldn’t be any issue with data loss or unrecoverable errors).

Thanks for the fix!

[bchastanier (Benjamin Chastanier)]

Hello @clemg,

Fix has landed, you can now downsize a DB disk if this DB has never been deployed.

Let me know if you need further assistance,

Cheers