Sets cgroup v1 in Fedora +31

[electrocucaracha]

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind api-change

/kind bug

/kind cleanup
/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake

What this PR does / why we need it:
Kubelet service doesn't start if CRI-O is selected as runtime manager for Fedora distros

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:
Use container_manager: crio on a Fedora +31 release

Does this PR introduce a user-facing change?:
NONE

[k8s-ci-robot]

Hi @electrocucaracha. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[floryut]

/approve
/ok-to-test

[oomichi]

/cc @oomichi

[oomichi]

How about using block: for merging when conditions into a single one like

- block:
  - name: disable unified_cgroup_hierarchy in Fedora 31+
     command: grubby --update-kernel=ALL --args="systemd.unified_cgroup_hierarchy=0"
  - name: reboot in Fedora 31+
     reboot:
  when:
    - ansible_distribution == "Fedora"
    - (ansible_distribution_major_version | int) >= 31
    - ansible_proc_cmdline['systemd.unified_cgroup_hierarchy'] is not defined or ansible_proc_cmdline['systemd.unified_cgroup_hierarchy'] != '0'

for the readability?

[electrocucaracha]

I like the idea, I just wonder if should be nice to sync that with docker and containerd

[oomichi]

Nice point.
To keep the scope of this PR small and easy, It is better to create another PR for the above docker and containerd cases, I feel.

[mattymo]

We typically avoid blocks and instead use include_tasks module referencing another file in Kubespray. The code in this PR is just fine (2 tasks doesn't really merit a separate file, but 4+ would)

[mattymo]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: electrocucaracha, floryut, mattymo

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [floryut,mattymo]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment