PITR gets disabled after the database is Suspended and Resumed
Description
Tested with Everest vv0.0.0-74fd87c version.
Create a mysql database with 5 nodes. Enable scheduled backups and PITR.
Pod status
Suspend the database
Edit the backup schedule and modify it.
Resume the database. The database comes up but PITR is disabled
Pod status
PXC operator, everest operator, pod logs, pxc/mysql-x75 yaml attached.
Environment
None
Attachments
4
Activity
Manish Chawla March 26, 2025 at 3:14 PM
Tested with Everest v0.0.0-c25b0b1(1.6.0).
Tested this scenario with mysql, mongodb and pg. PITR does not get disabled after Suspending and Resuming the database. This does not seem to be an issue now, hence we can close it.
Oksana Grishchenko March 18, 2025 at 3:26 PM
Can’t reproduce it. The problem is quite old, probably it was fixed in the scopes of some other problem. Moving the ticket to Ready for QA so that QA could confirm the ticket can be closed. If so, we should remove the Fix versions 1.6.0 tag from the ticket.
Tested with Everest vv0.0.0-74fd87c version.
Create a mysql database with 5 nodes. Enable scheduled backups and PITR.
Pod status
Suspend the database
Edit the backup schedule and modify it.
Resume the database. The database comes up but PITR is disabled
Pod status
PXC operator, everest operator, pod logs, pxc/mysql-x75 yaml attached.