Support Rocky Linux when available

[cristicalin]

What would you like to be added:

Support Rocky Linux 8.3 when GA. For now RC is out but ansible 2.9 seems to have issues with it.

TASK [bootstrap-os : Assign inventory name to unconfigured hostnames (non-CoreOS, non-Flatcar, Suse and ClearLinux)] **********************************************************************************************
task path: /root/kubespray/roles/bootstrap-os/tasks/main.yml:52                                                                                                                                                   
fatal: [rocky.kaveman.intra]: FAILED! => {                                                                                                                                                                        
    "changed": false,                                                                                                                                                                                             
    "invocation": {                                                                                                                                                                                               
        "module_args": {                                                                                                                                                                                          
            "name": "rocky.kaveman.intra",                                                                                                                                                                        
            "use": null                                                                                                                                                                                           
        }                                                                                                                                                                                                         
    },                                                                                                                                                                                                            
    "msg": "hostname module cannot be used on platform Linux (Rocky)"                                                                                                                                             
}

I have seen a similar issue when adding AlmaLinux support, but that was fixed by moving to ansible 2.9.20. It seems ansible 2.9.21 (current 2.9) is still lacking support for Rocky so we may need to wait for the GA.

Why is this needed:

Rocky Linux together with AlmaLinux are trying to fill the void RedHat created when they killed off the traditional CentOS and replaced it with CentOS Streams. These follow much closer the releases of upstream RHEL and we should try to support them similar to other distributions.

[champtar]

@cristicalin can you make sure there is an Ansible issue for this ?

[cristicalin]

There are two open PRs tracking this in ansible upstream: ansible/ansible#74539 and ansible/ansible#74538. Both were closed due to ansible-2.9 being in security bug-fix and maintenance stage so actually supporting Rocky may require that we upgrade ansible to 2.11 at least as the only PRs still allowed are for 2.11 (see ansible/ansible#74561 and ansible/ansible#74560)

[cristicalin]

A first issue with testing 2.10 (not 2.11 yet): #7599

[cristicalin]

With the fix proposed in #7600 we may actually just need to bump to 2.10 when it gets the backports for Rocky. As far as I can tell, 2.10 should still get them.

[k8s-triage-robot]

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR 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 and PRs.

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

[k8s-triage-robot]

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

This bot triages issues and PRs 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:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

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

This bot triages issues and PRs 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:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close

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.