0081-ntp-configurations.yml Report an error

[MRjiangmb]

What happened?

fatal: [master01]: FAILED! => {"msg": "The conditional check 'ansible_facts.selinux.mode == 'enforcing'' failed. The error was: error while evaluating conditional (ansible_facts.selinux.mode == 'enforcing'): 'dict object' has no attribute 'mode'\n\nThe error appears to be in '/root/kubespray/roles/kubernetes/preinstall/tasks/0081-ntp-configurations.yml': line 84, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: Put SELinux in permissive mode, logging actions that would be blocked.\n ^ here\n"}

The installation reported an error

What did you expect to happen?

No errors

How can we reproduce it (as minimally and precisely as possible)?

I replaced

 kubespraybak/roles/kubernetes/preinstall/tasks/0081-ntp-configurations.yml
    - ansible_facts.selinux.mode == 'enforcing' 

with
- ansible_facts.selinux.status == 'enforcing'
Error elimination

OS

Other|Unsupported

Version of Ansible

almalinux 10
ansible [core 2.17.14]

Version of Python

3.12.9

Version of Kubespray (commit)

2.29.1

Network plugin used

cilium

Full inventory with variables

ansible-playbook -i inventory/mycluster/inventory.ini --become --become-user=root --tags cluster.yml

Command used to invoke ansible

ansible-playbook

Output of ansible run

ansible-playbook -i inventory/mycluster/inventory.ini --become --become-user=root --tags cluster.yml

Anything else we need to know

No response

[tico88612]

@bbaassssiiee could you take a look on this?

[tico88612]

The issue you wrote should be the latest updated PR #12436.

But I remember it wasn't backported to 2.29 (so this should not happen on 2.29.1).

https://docs.ansible.com/projects/ansible/latest/playbook_guide/playbooks_vars_facts.html

I checked the Ansible docs, ansible_facts.selinux.status only enabled or disabled, not enforcing etc.

[MRjiangmb]

In previous installations, I didn't set the time zone in all.yml, and no errors occurred. However, after I set the time zone, errors started to appear. After I changed it to "status", subsequent installations did not report any errors.

[tico88612]

But I want to clarify, did this happen in master or in 2.29.1? Because you wrote it in 2.29.1.

[tico88612]

@MRjiangmb I'm guessing that if the status isn't enabled, then the mode probably isn't defined.

Can you print ansible_facts.selinux output?

[MRjiangmb]

But I want to clarify, did this happen in master or in 2.29.1? Because you wrote it in 2.29.1.但我想确认一下，这是在主版本还是2.29.1版本中发生的？因为你是在2.29.1版本写的。
I used git clone without specifying a version.

[MRjiangmb]

@MRjiangmb I'm guessing that if the status isn't enabled, then the mode probably isn't defined.我猜如果状态未启用，那模式可能也没被定义。

Can you print ansible_facts.selinux output?你能打印 ansible_facts.selinux 的输出吗？

ok: [10.1.66.11] => {
    "ansible_facts.selinux": {
        "status": "disabled"
    }
}

This is the current status, but when the error was reported, I checked and it was in the enable.

[tico88612]

status check needs to be added.

/triage accepted