Kata doesn't work on cgroupv2 with kubespray

[MrFreezeex]

The kata role doesn't work on cgroupv2 only distro (i.e: ubuntu22 apparently). Our testinfra unitest that calls kata-runtime check is failing and is reporting that kata containers can't be created.

See https://gitlab.com/kargo-ci/kubernetes-sigs-kubespray/-/jobs/4352349900

[oomichi]

Thanks for reporting this issue.

As https://gitlab.com/kargo-ci/kubernetes-sigs-kubespray/-/jobs/4401520415 the details are

=================================== FAILURES ===================================
______________________ test_run_check[ansible://ubuntu20] ______________________
host = <testinfra.host.Host ansible://ubuntu20>
    def test_run_check(host):
        kataruntime = "/opt/kata/bin/kata-runtime"
        with host.sudo():
            cmd = host.command(kataruntime + " check")
>       assert cmd.rc == 0
E       assert 1 == 0
E        +  where 1 = CommandResult(command=b"sudo /bin/sh -c '/opt/kata/bin/kata-runtime check'", exit_status=1, stdout=None, stderr=b'time...ners" arch=amd64 name=kata-runtime pid=5435 source=runtime\nERROR: System is not capable of running Kata Containers\n').rc
molecule/default/tests/test_default.py:21: AssertionError

[VannTen]

Probably relevant : https://github.com/kata-containers/documentation/blob/master/design/host-cgroups.md#cgroups-v2

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[VannTen]

/remove-lifecycle rotten /lifecycle frozen