tests: Work around bcvk hang in nested virt

GitHub Actions runners are nested VMs, and bcvk's use of virtiofs
causes systemd-journald to enter a livelock when writing to persistent
storage in nested virtualization environments.

Add the kernel argument systemd.journald.storage=volatile to force
journald to use tmpfs instead, which avoids the livelock.

This workaround is needed until bcvk issue #90 is fully resolved
upstream.

Fixes: #1708 (comment)
Related: bootc-dev/bcvk#90

Assisted-by: Claude Code (Sonnet 4.5)

Author: cgwalters

.github/workflows/ci.yml

@@ -125,9 +125,7 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        # TEMPORARILY TESTING ONLY C9S FOR DEBUGGING
-        test_os: [centos-9]
-        # test_os: [fedora-42, fedora-43, centos-9, centos-10]
+        test_os: [fedora-42, fedora-43, centos-9, centos-10]
 
     runs-on: ubuntu-24.04
 
@@ -138,13 +136,6 @@ jobs:
         with:
           libvirt: true
 
-      - name: Setup upterm session for debugging
-        uses: owenthereal/action-upterm@v1
-        with:
-          limit-access-to-actor: false
-          limit-access-to-users: cgwalters
-          wait-timeout-minutes: 60
-
       - name: Build container and disk image
         run: |
           tests/build.sh ${{ matrix.test_os }}
@@ -166,9 +157,7 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        # TEMPORARILY TESTING ONLY C9S FOR DEBUGGING
-        test_os: [centos-9]
-        # test_os: [fedora-42, fedora-43, centos-9, centos-10]
+        test_os: [fedora-42, fedora-43, centos-9, centos-10]
 
     runs-on: ubuntu-24.04
 

Justfile

@@ -33,7 +33,7 @@ build-install-test-image: build-integration-test-image
     cd hack && podman build -t localhost/bootc-integration-install -f Containerfile.drop-lbis
 
 build-disk-image container target:
-    bcvk to-disk --format=qcow2 --disk-size 20G --filesystem ext4 {{container}} {{target}}
+    bcvk to-disk --format=qcow2 --disk-size 20G --filesystem ext4 --karg systemd.journald.storage=volatile {{container}} {{target}}
 
 # These tests accept the container image as input, and may spawn it.
 run-container-external-tests: