[QE]remove okd preset test on arm64

Author: lilyLuLiu

images/build-e2e/lib/darwin/run.sh

@@ -50,7 +50,8 @@ done
 mkdir -p $targetFolder/results
 
 # Run tests
-tags="darwin"
+arch=$(uname -m)
+tags="$arch,darwin"
 if [ ! -z "$e2eTagExpression" ]
 then
     tags="$tags && $e2eTagExpression"

images/build-e2e/lib/linux/run.sh

@@ -50,7 +50,8 @@ done
 mkdir -p $targetFolder/results
 
 # Run tests
-tags="linux"
+arch=$(uname -m)
+tags="$arch,linux"
 if [ ! -z "$e2eTagExpression" ]
 then
     tags="$tags && $e2eTagExpression"

images/build-e2e/lib/windows/run.ps1

@@ -24,7 +24,7 @@ $resultsDir = "$targetFolderDir\results"
 New-Item -ItemType directory -Path "$resultsDir" -Force
 
 # Run tests
-$tags="windows"
+$tags="amd64,windows"
 if ($e2eTagExpression) {
     $tags="$tags && $e2eTagExpression"
 }

test/e2e/features/config.feature

@@ -162,7 +162,6 @@ Feature: Test configuration settings
         And stdout should contain "Successfully unset configuration property 'preset'"
         And "JSON" config file "crc.json" in CRC home folder does not contain key "preset"
 
-
     Scenario: CRC config set and get preset property (positive cases) 
         When setting config property "preset" to value "<preset-value>" succeeds
         And "JSON" config file "crc.json" in CRC home folder contains key "preset" with value matching "<preset-value>" 
@@ -172,11 +171,16 @@ Feature: Test configuration settings
         And stdout should contain "Successfully unset configuration property 'preset'"
         And "JSON" config file "crc.json" in CRC home folder does not contain key "preset"
 
-        @linux @darwin @windows 
+        @x86_64
         Examples: Config property preset setting positive
             | preset-value  |
             | microshift    | 
             | okd           | 
+
+        @arm64
+        Examples: Config property preset setting positive
+            | preset-value  |
+            | microshift    | 
 
     Scenario: CRC config set preset (negtive cases) 
         When setting config property "preset" to value "<preset-value>" fails