tests: Add solution upgrade test

Before this the solution-next ISO was not used at all,
so let's fix it and add a simple test for solution upgrade

Author: TeddyAndrieux

.github/workflows/multi-node-test.yaml

@@ -62,7 +62,7 @@ on:
         description: "The solution version to install"
         required: false
         type: string
-        default: "1.1.0"
+        default: "1.1.1"
       solution-base-url:
         description: "The URL to download the solution"
         required: false

.github/workflows/single-node-test.yaml

@@ -226,7 +226,7 @@ jobs:
         if: inputs.test-solution
         uses: ./.github/actions/bastion-tests
         with:
-          PYTEST_FILTERS: "solution"
+          PYTEST_FILTERS: "solution-upgrade"
       - name: Run tests from Bastion
         uses: ./.github/actions/bastion-tests
         with:

tests/post/features/solutions.feature

@@ -23,3 +23,39 @@ Feature: Solutions
         And we delete the Solution Configuration file
         Then we have no Solution 'example-solution' archive mounted
         And we have no Solution Configuration file present
+
+    @solution-upgrade
+    Scenario: Upgrade Solution
+        Given the Kubernetes API is available
+        And no Solution 'example-solution' is imported
+        And no Solution environment 'example-environment' is available
+        And the Solution Configuration file is absent
+        When we import a Solution archive '/var/tmp/example-solution.iso'
+        Then Solution archive 'example-solution' is imported correctly
+        And Solution 'example-solution' version '1.1.0' is available
+        When we activate Solution 'example-solution' version '1.1.0'
+        Then Solution 'example-solution' version '1.1.0' is activated
+        And CRD 'versionservers.metalk8s-solution-example.scality.com' exists in Kubernetes API
+        And CRD 'clockservers.metalk8s-solution-example.scality.com' exists in Kubernetes API
+        When we create a solution environment 'example-environment'
+        Then solution environment 'example-environment' is available
+        When we deploy Solution 'example-solution' in environment 'example-environment' with version '1.1.0'
+        Then we have 1 running pod labeled 'app=example-solution-operator' in namespace 'example-environment'
+        When we import a Solution archive '/var/tmp/example-solution-next.iso'
+        Then Solution archive 'example-solution-next' is imported correctly
+        And Solution 'example-solution-next' version '1.1.1' is available
+        When we activate Solution 'example-solution-next' version '1.1.1'
+        Then Solution 'example-solution-next' version '1.1.1' is activated
+        And CRD 'versionservers.example-solution-next.metalk8s.scality.com' exists in Kubernetes API
+        And CRD 'clockservers.example-solution-next.metalk8s.scality.com' exists in Kubernetes API
+        When we deploy Solution 'example-solution' in environment 'example-environment' with version '1.1.1'
+        Then we have 1 running pod labeled 'app=example-solution-operator,app.kubernetes.io/version=1.1.1' in namespace 'example-environment'
+        When we unimport Solution archive '/var/tmp/example-solution.iso'
+        Then we have 1 running pod labeled 'app=example-solution-operator' in namespace 'example-environment'
+        When we deactivate Solution 'example-solution'
+        And we delete Solution 'example-solution' in environment 'example-environment'
+        And we delete Solution environment 'example-environment'
+        And we unimport Solution archive '/var/tmp/example-solution-next.iso'
+        And we delete the Solution Configuration file
+        Then we have no Solution 'example-solution' archive mounted
+        And we have no Solution Configuration file present