Issues
- [UI] DB engine upgrade wrongly updates backup schedule timeEVEREST-1979Fábio Da Silva
- [UI] PITR location not correctly set when restoring from a backupEVEREST-1978Fábio Da Silva
- Disable DB operations during upgrades and disk resizesEVEREST-1950Fábio Da Silva
- Mongodb database toggles between Initializing and Down statusEVEREST-1936
- [UI] PITR time can't be changed from the last successful backupEVEREST-1895Fábio Da Silva
- [UI] Conflict when backup schedules are deletedEVEREST-1868Fábio Da Silva
- [CLI] User entered namespace is not accepted, default namespace is installedEVEREST-1846Maxim Kondratenko
- Database restores are not reconciled correctly for any DB typeEVEREST-1820Mayank Shah
- 5 node sharded mongodb cluster is unable to come upEVEREST-1412
[UI] DB engine upgrade wrongly updates backup schedule time
Description
Environment
Attachments
blocks
Activity
Manish ChawlaApril 10, 2025 at 12:07 PM
Tested with FB Feature build · percona/everest@0a984e5
Install 1.5.0 using cli, a1 namespace has mysql, a2 namespace has pg.
Create a mysql db in a1 namespace.
Create a pg db of 3 nodes for 16.3. Enable scheduled backups and PITR. Enable monitoring. Enable external access. Add 3 scheduled backups with different backup storages.
Create a pg db of 1 node for 13.15. Enable scheduled backups and PITR. Add 3 scheduled backups with different backup storages.
Create a pg db of 2 nodes for 15.7. Enable scheduled backups and PITR. Add 3 scheduled backups with different backup storages.
Add data in all db. Take scheduled backup of all pg db.
Backup schedules of pg db 16.3
Upgrade to FB
Upgrade the pg operator. Pg operator requires the db versions to be upgraded. Upgrade pg 16.3 to 16.4.
After upgrading the pg db to 16.4, the backup schedules time remained the same as before. Upgraded the pg operator to 2.6.0, then upgraded the crd. After all the upgrades were completed, there was no change in the backup schedules time
Upgraded all the pg db and did not observe any change in the backup schedules time.
Fábio Da SilvaApril 9, 2025 at 3:47 PM
@Manish Chawla new FB: https://github.com/percona/everest/actions/runs/14361463938
Thanks
Manish ChawlaApril 9, 2025 at 1:45 PM
Tested with FB Feature build · percona/everest@e21d85f
Install 1.5.0 using cli, a1 namespace has mysql, a2 namespace has pg.
Create a mysql db in a1 namespace.
Create a pg db of 3 nodes for 16.3. Enable scheduled backups and PITR. Enable monitoring. Enable external access. Add 3 scheduled backups with different backup storages.
Create a pg db of 1 node for 13.15. Enable scheduled backups and PITR. Add 3 scheduled backups with different backup storages.
Create a pg db of 2 nodes for 15.7. Enable scheduled backups and PITR. Add 3 scheduled backups with different backup storages.
Add data in all db. Take scheduled backup of all pg db.
Backup schedules of pg db 16.3
Upgrade to FB
Upgrade the pg operator
Pg operator requires the db versions to be upgraded. Upgrade pg 16.3 to 16.4
After upgrading the pg db to 16.4, the backup schedules time change
STR:
Install Everest 1.5.0
Create a PG DB using 16.3 with a backup schedule
Upgrade Everest (using this FB)
Go to the Namespaces page and try to upgrade PGO to 2.6.0
You will be prompted to first upgrade the DB to PG 16.4. Click the button to upgrade.
Upon upgrading to PG 16.4, the timings of the backup schedules are updated.
Cause:
Upon further investigation, it was observed that on upgrading the DB to a new version, the UI wrongly updates the backup schedule time in the update request.
As an unintended side effect, the backup schedule time is also updated.
Example:
In screenshot (1), we have created a PG DB 16.3 with schedule that runs at 5:00 pm (IST).
This translates to a
11 30 * * *in the cron format, as seen from screenshot (2) where we make a GET request to this DB.In screenshot (3), we click the DB version update button on the operator upgrade screen. Here you can see that the UI wrongly updates the schedule to
0 6 * * *