fix task naming in bootstrap-os

[ErikJiang]

What type of PR is this?

/kind bug

What this PR does / why we need it:

The naming of some task files in bootstrap-os doesn't match the ID values in the actual os-release file, which will cause the related OS tasks not to be executed.

# nerdctl run --rm clearlinux:latest cat /etc/os-release |grep "^ID="
ID=clear-linux-os

# nerdctl run --rm redhat/ubi8:8.10 cat /etc/os-release |grep "^ID="
ID="rhel"

Which issue(s) this PR fixes:

Fixes #11712

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

fix task naming in bootstrap-os

[MrFreezeex]

Does this apply in those other places:

❯ find | grep -E '(redhat|clearlinux)'
./roles/container-engine/docker/vars/redhat-7.yml
./roles/container-engine/docker/vars/clearlinux.yml
./roles/container-engine/docker/vars/redhat.yml
./roles/bootstrap-os/tasks/clearlinux.yml
./roles/bootstrap-os/tasks/redhat.yml
./roles/kubernetes-apps/helm/vars/redhat-7.yml
./roles/kubernetes-apps/helm/vars/redhat.yml
./roles/adduser/vars/redhat.yml
./roles/network_plugin/calico/vars/redhat-9.yml
./roles/network_plugin/calico/vars/redhat.yml

too?

[ErikJiang]

@MrFreezeex
It currently seems that only the bootstrap-os role parses the os-release file to identify different OS distributions.
In contrast, other roles primarily differentiate based on ansible_distribution.
Therefore, only the bootstrap-os role needs to be modified.
The reason why the bootstrap-os role does not use the ansible_distribution method remains unclear.
I suspect the information obtained through ansible_distribution may not fully meet the requirements for identifying different OS within bootstrap-os.

[MrFreezeex]

Ah indeed makes sense, I am guessing that we don't have this fact yet in the bootstrap phase and thus we need to get it via another way which is unfortunately not consistent with other places :/

/lgtm

[VannTen]

/ok-to-test
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ErikJiang, MrFreezeex, VannTen

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 [VannTen]

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

[VannTen]

/retest

[VannTen]

/cherrypick release-2.25
/cherrypick release-2.26

[k8s-infra-cherrypick-robot]

@VannTen: new pull request created: #11718

In response to this:

/cherrypick release-2.25
/cherrypick release-2.26

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-sigs/prow repository.

[k8s-infra-cherrypick-robot]

@VannTen: new pull request created: #11719

In response to this:

/cherrypick release-2.25
/cherrypick release-2.26

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-sigs/prow repository.