E2E tests - Improve uninstall checks
Description
Activity
Edith Erika Puclla Pareja yesterdayEdited
Talking with @Tomislav Plavcic I will approach this task with the following:
Implement a validation after the uninstallation of Percona Everest (everest-qa workflows)
Validation check Kubernetes Objects. (Uninstall if they are present)
Check if Everest Namespace is Removed
Check if Everest Deployments are Removed
Check if Everest CRDs Were Removed
Check if Everest PVCs (Persistent Volumes) Were Removed
Check for Leftover Everest Services
Check if Everest Helm Release is Still Listed (if Installed via Helm)
Do this validation for:
The Upgrade workflow
GKE workflow
EKS workflow
Run the Workflow Locally
Check the output of the "Validate Everest Uninstall" step.
We need to
tail
the uninstall command to some file and check that the output contains the proper message "Everest was uninstalled."we “tee“ the upgrade command: https://github.com/percona/everest-qa/blob/main/.github/workflows/upgrade.yml#L429 so we need to do the same with the uninstall command and then check that the output includes the message that it was a success
Details
Details
Assignee
Reporter
Priority
Smart Checklist
Open Smart Checklist
Smart Checklist

Currently we run everestctl uninstall only in the upgrade test at the end, but we don’t check if the correct message was displayed and also were all the namespaces and kubernetes objects destroyed.
Also we need to add uninstall command in the GKE/EKS/OpenShift workflows for normal tests as well, together with all the checks.
here: https://github.com/percona/everest-qa/blob/main/.github/workflows/upgrade.yml#L502
we have uninstall, but we don't check anything about it
and here: https://github.com/percona/everest-qa/blob/main/.github/workflows/everest-qa-GKE-workflow.yml
we don't even have uninstall, so we need to add uninstall and also add some checks
here the same: https://github.com/percona/everest-qa/blob/main/.github/workflows/everest-qa-EKS-workflow.yml