Cannot delete database

INFORMATION

Relevant information to this issue:

  • OS:
  • databases: PostgreSQL AND Redis

https://console.qovery.com/organization/12e0c625-6fb8-434b-adeb-041614fa7a46/project/a7f79a8f-8c0e-46a5-8748-1ba9846481c9/environment/ac7a73ea-1a51-4ee2-92f7-8a9737f1691e/services/general

https://console.qovery.com/organization/12e0c625-6fb8-434b-adeb-041614fa7a46/project/a7f79a8f-8c0e-46a5-8748-1ba9846481c9/environment/728025c3-48dd-41b2-b53f-aca8c4b02394/services/general

https://console.qovery.com/organization/12e0c625-6fb8-434b-adeb-041614fa7a46/project/a7f79a8f-8c0e-46a5-8748-1ba9846481c9/environment/8ba37471-3aa4-4d3e-a567-f3cc1d338abb/services/general

https://console.qovery.com/organization/12e0c625-6fb8-434b-adeb-041614fa7a46/project/a7f79a8f-8c0e-46a5-8748-1ba9846481c9/environment/76ac7b12-363a-47ce-8464-0b237483f930/services/general

ISSUE

When we try to delete an environment, the deletion gets canceled. We can delete each application or lifecycle one by one but we can’t delete any database.

For Redis we get the following logs:


And for PostgreSQL:


How could I force delete the database I’d like to delete?
Can I delete them from AWS? Will the deletion be replicated on Qovery?

Hey @jmeiss !

This is a regression we just introduced, a patch is on it’s way, I will let you now once fixed.
Status here => Database operations (create / update / delete) are failing – Incident details - Qovery Status

Sorry for the inconvenience,
Benjamin

1 Like

Hey @jmeiss,

Should be good now, can you test again?

Cheers

Yes I confirm that it’s fixed. Thx

1 Like

Actually it worked for all environments but that one couldn’t be deleted:

https://console.qovery.com/organization/12e0c625-6fb8-434b-adeb-041614fa7a46/project/a7f79a8f-8c0e-46a5-8748-1ba9846481c9/environment/76ac7b12-363a-47ce-8464-0b237483f930/services/general

Probably for another reason since all the services have been deleted but I’m unable to delete the environment :confused:

Indeed, since to be a weird glitch on our end, need to be investigated, might be caused by job called on delete.

Keep you posted :slight_smile:

1 Like

Yeah it’s most likely linked to our script called on delete that didn’t find a CNAME record on Route 53 since the deployment on environment creation didn’t succeed

Hi @bchastanier ,

May I ask you to delete the following environment I can’t delete by myself?
https://console.qovery.com/organization/12e0c625-6fb8-434b-adeb-041614fa7a46/project/a7f79a8f-8c0e-46a5-8748-1ba9846481c9/environment/76ac7b12-363a-47ce-8464-0b237483f930/services/general

Or do you prefer to keep it in order to investigate where the bug comes from?

Hey @jmeiss,

Sure, I am deleting it.

Cheers

1 Like

Thanks a lot @bchastanier :pray:

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.