added GH workflow to manually trigger multihost tests

Fixes: #841

Signed-off-by: Michael Engel <[email protected]>

.github/workflows/integration-tests.yml

@@ -94,7 +94,11 @@ jobs:
       - name: Run integration tests
         run: |
           cd tests
-          tmt run -v -eCONTAINER_USED=integration-test-local -eWITH_COVERAGE=1 -eLOG_LEVEL=DEBUG
+          tmt run -v \
+            -eCONTAINER_USED=integration-test-local \
+            -eWITH_COVERAGE=1 \
+            -eLOG_LEVEL=DEBUG \
+            plan --name container
 
       - name: Show tmt log output in case of failure
         if: ${{ failure() }}
@@ -106,8 +110,8 @@ jobs:
       - name: Extract coverage results
         if: always()
         run: |
-          MERGE_FILE="/var/tmp/tmt/run-001/plans/tier0/report/default-0/merged.info"
-          COVERAGE_DIR="/var/tmp/tmt/run-001/plans/tier0/report/default-0/report/"
+          MERGE_FILE="/var/tmp/tmt/run-001/plans/container/report/default-0/merged.info"
+          COVERAGE_DIR="/var/tmp/tmt/run-001/plans/container/report/default-0/report/"
           if [ -d "$COVERAGE_DIR" ]; then
             cp -r $COVERAGE_DIR /var/tmp
             cp $MERGE_FILE /var/tmp

.github/workflows/multihost-tests.yml

@@ -0,0 +1,36 @@
+name: Integration tests in multi-host mode
+
+on:
+  workflow_dispatch:
+
+jobs:
+
+  ghrelease:
+    name: Run Integration Tests on testing farm in multihost mode
+    runs-on: ubuntu-latest
+    container:
+      image: quay.io/bluechi/build-base:latest
+
+    steps:
+      - name: Checkout sources
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+          submodules: 'true'
+
+      - name: Install testing farm CLI
+        run: |
+          python3 -m ensurepip --default-pip
+          python3 -m pip install --upgrade pip
+          python3 -m pip install tft-cli
+
+      - name: Start Integration Tests on testing farm
+        run: |
+          testing-farm version
+          TESTING_FARM_API_TOKEN=${{ secrets.TESTING_FARM_API_TOKEN }} testing-farm request \
+            --path tests \
+            --git-ref add-multihost-workflow \
+            --git-url https://github.com/eclipse-bluechi/bluechi.git \
+            --compose Fedora-Rawhide \
+            --plan multihost \
+            --pipeline-type tmt-multihost

.packit.yml

@@ -45,6 +45,7 @@ jobs:
     trigger: pull_request
     identifier: integration-tests
     fmf_path: tests
+    tmt_plan: container
     labels:
       - standard
     env:
@@ -58,6 +59,7 @@ jobs:
     trigger: pull_request
     identifier: integration-tests-valgrind
     fmf_path: tests
+    tmt_plan: container
     labels:
       - valgrind
     env:

tests/README.md

@@ -71,21 +71,23 @@ systemctl --user start podman.socket
 
 Integration tests are executed with [tmt framework](https://github.com/teemtee/tmt).
 
-To run integration tests please execute below command of the top level directory of this project:
+To run integration tests please execute below command in the [tests](./) directory:
 
 ```shell
-tmt run -v
+tmt run -v plan --name container
 ```
 
 This will use latest BlueChi packages from
 [bluechi-snapshot](https://copr.fedorainfracloud.org/coprs/g/centos-automotive-sig/bluechi-snapshot/) repository.
 
+**Note:** The integration tests can be run in two modes - container and multi-host. For local execution it is advised to select `container` mode (hence the `plan --name container`).
+
 ## Running integration tests with memory leak detection
 
 To run integration tests with `valgrind`, set `WITH_VALGRIND` environment variable as follows:
 
 ```shell
-tmt run -v -eWITH_VALGRIND=1
+tmt run -v -eWITH_VALGRIND=1 plan --name container
 ```
 
 If `valgrind` detects a memory leak in a test, the test will fail, and the logs will be found in the test `data` directory.
@@ -122,7 +124,7 @@ After that step integration tests can be executed using following command:
 
 ```shell
 cd ~/bluechi/tests
-tmt run -v -eCONTAINER_USED=integration-test-local
+tmt run -v -eCONTAINER_USED=integration-test-local plan --name container
 ```
 
 ## Creating code coverage report from integration tests execution
@@ -139,7 +141,7 @@ createrepo_c ~/bluechi/tests/bluechi-rpms
 When done, you need to run integration tests with code coverage report enabled:
 
 ```shell
-tmt run -v -eCONTAINER_USED=integration-test-local -eWITH_COVERAGE=1
+tmt run -v -eCONTAINER_USED=integration-test-local -eWITH_COVERAGE=1 plan --name container
 ```
 
 After the integration tests finishes, the code coverage html result can be found in `res` subdirectory inside the tmt
@@ -173,7 +175,7 @@ More detailed information can be displayed by setting log level to `DEBUG`:
 
 ```shell
 cd ~/bluechi/tests
-tmt run -v -eLOG_LEVEL=DEBUG
+tmt run -v -eLOG_LEVEL=DEBUG plan --name container
 ```
 
 ### Using python bindings in tests

tests/plans/tier0.fmf → tests/plans/container.fmf

@@ -1,4 +1,4 @@
-summary: Tier 0 - Basic functionality tests
+summary: Running Integration Tests with containers
 discover:
     how: fmf
     filter: tier:0

tests/plans/multihost.fmf

@@ -0,0 +1,44 @@
+summary: Running Integration Tests with multiple hosts
+provision:
+    - name: test-executor
+      role: executor
+    - name: bluechi-controller
+      role: controller
+    - name: bluechi-agent-1
+      role: agent
+    - name: bluechi-agent-2
+      role: agent
+environment:
+    BLUECHI_CTRL_SVC_PORT: 8420
+
+    INSTALL_EXECUTOR_DEPS: yes
+    INSTALL_WORKER_DEPS: yes
+
+    SETUP_SSH: yes
+    SSH_USER: root
+    SSH_PASSWORD: root
+
+    LOG_LEVEL: DEBUG
+    WITH_COVERAGE: 0
+    WITH_VALGRIND: 0
+discover:
+    how: fmf
+    filter: tag:multihost
+    where: executor
+prepare:
+    - name: Prepare executor setup
+      how: shell
+      script: |
+          ./scripts/tests-setup.sh setup_multihost_test setup_executor
+      where: executor
+    - name: Prepare worker setup
+      how: shell
+      script: |
+          ./scripts/tests-setup.sh setup_multihost_test setup_worker
+      where: 
+        - controller
+        - agent
+execute:
+    how: tmt
+report:
+    how: junit