[UI] Database version can be changed when restoring to a new database
Description
Tested with Everest v1.2.0-rc3 version.
Install mongodb operator on a fresh gke cluster
Create a mongodb sharded database with version 7.0.12-7
Add some data and shard it. Then take a scheduled backup.
Create a new database from full backup
The create database wizard shows all the mongodb versions available. Using this a user can downgrade/upgrade the mongodb version from 7.0.12-7 to 5.0.14-12 or vice versa in a restored database.
In previous release, the database version could not be changed in the restored database. This looks to be an issue.
Also, there is no error from backend api on database creation with lower version.
Environment
None
Attachments
9
Activity
Manish Chawla
December 24, 2024 at 1:17 PM
Tested with Everest v1.4.0-rc3 version.
Create mysql, mongodb and pg databases. Take some backups for the databases.
Create a new mongodb database from backup
The Database version can’t be changed.
Same for mysql and pg
The issue is fixed.
Manish Chawla
December 20, 2024 at 12:06 PM
Tested with Everest v1.4.0-rc2 version and found that the issue is coming again
The Database version can be changed during the creation of a new database from backup.
Manish Chawla
November 25, 2024 at 10:15 AM
Tested with Everest v0.0.0-d4306ed version.
Create a mongodb sharded database with version 7.0.12-7, take a scheduled backup.
Create a new database from PITR
Now the database version of the new database can’t be changed and is the same as the original database. Checked in mysql and postgresql databases also and it is the same behavior.
Tested with Everest v1.2.0-rc3 version.
Install mongodb operator on a fresh gke cluster
Create a mongodb sharded database with version 7.0.12-7
Add some data and shard it. Then take a scheduled backup.
Create a new database from full backup
The create database wizard shows all the mongodb versions available. Using this a user can downgrade/upgrade the mongodb version from 7.0.12-7 to 5.0.14-12 or vice versa in a restored database.
In previous release, the database version could not be changed in the restored database. This looks to be an issue.
Also, there is no error from backend api on database creation with lower version.