[CLI] Upgrade command is not clear

Description

Cli version

Frontend and backend version is Everest v0.5.0-22-g4995f22

Install operators using cli

The csv, subscription and catalog details are

Now run the upgrade command

The upgrade command displays that the catalog, subscriptions and everest have been upgraded.

Check the csv, subscription and catalog details again

They are the same as before running the upgrade command and there is no difference.

Issues
1. The upgrade command does not clearly display which catalog, subscription, everest operator version was upgraded. For example, it should clearly display:
Upgrading Percona Catalog from version X to version Y
Upgrading Everest operator from version X to version Y

2. If the catalog, subscriptions, everest operator are on the latest versions, then the upgrade command should not run the upgrade and display that these have been upgraded. Instead, it should display:
Percona Catalog is on the latest version Y and further upgrades are not available. Skipping upgrade.

Environment

None

Attachments

1

Activity

Manish Chawla May 7, 2024 at 12:19 PM

The new upgrade command does not have the previous issues, hence closing this issue.

Manish Chawla May 6, 2024 at 2:38 PM

The upgrade command in Everest v0.10.0 has the following help

Tested upgrade from Everest v0.9.1 to Everest v0.10.0.

Install 0.9.1

Create a mysql database with 1 node, enable scheduled backup and PITR.

Install mongodb operator in n2 namespace

Create a mongodb database with 1 node, enable scheduled backup and PITR.

Install postgresql operator in n1 namespace

Create a postgresql database with 1 node, enable scheduled backup and PITR.

Add data in all databases.

Status of csv, sub and ip in 0.9.1 release

Upgrade to 0.10.0

Status of csv, sub and ip in 0.10.0 release

The upgrade is successful from 0.9.1 to 0.10.0. The Everest UI displays the 0.10.0 version after refresh

On running the upgrade again

Hence cli detects that this is the latest version and does not run upgrade again.

Diogo Recharte May 6, 2024 at 9:55 AM

I think that with the work done in 0.10.0 we can consider this ticket as Done but please check.

Done

Details

Assignee

Reporter

Fix versions

Affects versions

Priority

Smart Checklist

Created December 12, 2023 at 1:27 PM
Updated May 7, 2024 at 12:19 PM
Resolved May 7, 2024 at 12:19 PM