tests: Update tests to use the new Solution version 1.1.0

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.0.2"
+        default: "1.1.0"
       solution-base-url:
         description: "The URL to download the solution"
         required: false

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

@@ -59,7 +59,7 @@ on:
         description: "The solution version to install"
         required: false
         type: string
-        default: "1.0.2"
+        default: "1.1.0"
       solution-base-url:
         description: "The URL to download the solution"
         required: false
@@ -74,7 +74,7 @@ on:
         description: "The next solution version to upgrade to (only used when `test-solution` enabled)"
         required: false
         type: string
-        default: "1.0.3"
+        default: "1.1.1"
 
 env:
   NAME: single-node-${{ inputs.os }}-${{ inputs.setup-idp && 'idp' || 'no-idp' }}-${{ inputs.setup-logging && 'logging' || 'no-logging' }}

tests/post/features/solutions.feature

@@ -7,14 +7,14 @@ Feature: Solutions
         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.0.2' is available
-        When we activate Solution 'example-solution' version '1.0.2'
-        Then Solution 'example-solution' version '1.0.2' is activated
-        And CRD 'versionservers.example-solution.metalk8s.scality.com' exists in Kubernetes API
-        And CRD 'clockservers.example-solution.metalk8s.scality.com' exists in Kubernetes API
+        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.0.2'
+        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 deactivate Solution 'example-solution'
         And we delete Solution 'example-solution' in environment 'example-environment'