Skip to:
Steps to reproduce:
Create a PG cluster;
Do a full backups;
Restore to a new DB from that backup;
After going through the backups step, the error icon will show up on the sidebar at the backup step;
Going back to the backups step removes the error icon
Tested with FB EVEREST-1978 | keep PITR location from selected cluster backup · percona/everest@250974c
Install 1.5.0 using cli, a1 namespace has mysql, a2 namespace has pg.
Create a pg database with 3 nodes, enable scheduled backups and PITR
Upgrade to FB, upgrade db version, upgrade pg operator 2.6.0, and upgrade crd.
Create a new database from PITR, no errors are displayed
The database is created successfully.
Created another database using full backup, there were no errors, and the database was created successfully.
Tested creating a new db using PITR of pg database having 2 and 1 nodes with different versions and did not observe any issue.
FB:
Steps to reproduce:
Create a PG cluster;
Do a full backups;
Restore to a new DB from that backup;
After going through the backups step, the error icon will show up on the sidebar at the backup step;
Going back to the backups step removes the error icon