Issues

Select view

Select search mode

 
50 of 82

Deleting a database does not remove its restores

Done

Description

Tested in Everest v0.10.0-rc5 version.

Create a mysql/mongodb database, enable scheduled backups and PITR.

After some backups, restore the same database using a backup.

After the database comes up, delete it. The database is removed, but the restore still remains in the namespace.

For example, this is the list of databases remaining

image-20240502-131222.png

These are the database restores

kubectl get dbr -n n1 NAME CLUSTER BACKUP PATH STORAGE STATUS COMPLETED AGE restore-4u3 restored-mysql-2 cron-restored-mysql-2-namespace1-202452113037-25ss9 Succeeded 40m 42m restore-8wa restored-mysql-aft-upg cron-restored-mysql-a-namespace1-2024529542-13hs9 Succeeded 168m 170m restore-f1c mysql-t22 cron-mysql-t22-namespace1-20245212050-6oioo Succeeded 18m 19m restore-idu mysql-qbv cron-mysql-qbv-namespace1-2024527547-13hs9 Succeeded 4h54m 4h55m restore-xz3 mysql-qbv cron-mysql-qbv-namespace1-2024529547-13hs9 Succeeded 130m 135m

The databases mysql-t22, restored-mysql-2, restored-mysql-aft-upg have been deleted but there restores are still remaining.

Environment

None

Attachments

3
  • 02 May 2024, 01:43 PM
  • 02 May 2024, 01:43 PM
  • 02 May 2024, 01:14 PM

Details

Assignee

Reporter

Sprint

Fix versions

Affects versions

Priority

Smart Checklist

Created May 2, 2024 at 1:14 PM
Updated May 3, 2024 at 1:14 PM
Resolved May 3, 2024 at 1:14 PM

Activity

Manish ChawlaMay 3, 2024 at 1:14 PM

This issue was not observed in Everest v0.10.0-rc6 version.

Manish ChawlaMay 2, 2024 at 1:43 PM

If recreate the database with the same name as deleted one, then it doesn't come up and the same restore gets associated with it

NAME SIZE READY STATUS HOSTNAME AGE mysql-t22 2 initializing mysql-t22-haproxy.n1 9m35s
image-20240502-134234.png
image-20240502-134259.png

Flag notifications