kunai "Back-off restarting failed container frontend-container" (CI failure)

Summary

kunai unit failure results in failing the deploy-management-cluster job in CI misc pipelines

Unit timeout exceeded: unit Kustomization/kunai did not became ready after 5m0s
The following resources were progressing and not ready:
IDENTIFIER                        STATUS     REASON           MESSAGE
Kustomization/sylva-system/kunai  InProgress                  Kustomization generation is 2, but latest observed generation is -1
╰┄╴HelmRelease/sylva-system/kunai InProgress                  HelmRelease generation is 1, but latest observed generation is -1
   ├┄╴┬┄┄[Conditions]
   ┆  ├┄╴Reconciling              True       Progressing      Running 'install' action with timeout of 5m0s
   ┆  ╰┄╴Ready                    Unknown    Progressing      Running 'install' action with timeout of 5m0s
   ╰┄╴┬┄┄[Events]
      ╰┄╴2025-11-23 22:35:26      Normal     HelmChartCreated Created HelmChart/sylva-system/sylva-system-kunai with SourceRef 'HelmRepository/sylva-system/unit-kunai'

in the artifact dump BackOff Back-off restarting failed container frontend-container in pod kunai-frontend-5b8b4b6d7-98mk7_kunai

2025-11-23T22:35:35Z    2025-11-23T22:38:23Z    kubelet-mgmt-2174787810-kubeadm-capm3-virt-management-cp-2      Pod     kunai-frontend-5b8b4b6d7-98mk7  6       Failed  "Error:
 failed to create containerd task: failed to create shim task:
 OCI runtime create failed:
 runc create failed:
 unable to start container process: error during container init:
 error mounting ""/var/lib/kubelet/pods/ee878a24-de9e-4f6d-843d-a4267b9ae96d/volumes/kubernetes.io~empty-dir/cache-volume"" to rootfs at ""/opt/app/.next/cache"":
 create mountpoint for /opt/app/.next/cache mount:
 make mountpoint ""/opt/app/.next/cache"":
 openat2 /run/containerd/io.containerd.runtime.v2.task/k8s.io/frontend-container/rootfs/opt/app/.next/cache:
 not a directory: unknown"

CI pipeline failure issue

The scheduled pipeline run for ☁️capm3 🚀kadm 🎬nightly 🛠️ha,misc 🐧ubuntu on 2025-11-24 has failed.

Report Details

  • Report Link
  • Failed Pipeline

Failing Jobs & Status

  • Overall Status: 🔴 Deployment/upgrade Failed
  • Failing Jobs:
  • delete-workload-cluster (failed)
  • deploy-management-cluster (failed)

This issue was auto-generated from the scheduled pipeline report. Please add any relevant notes below.

Assignee Loading
Time tracking Loading