On 16.09.2019 15:45, Keith Mills wrote:
Hi Stefan,

I'm working on a task for SELinux that I need to install dependencies, set SELinux to permissive mode, etc. This is for RHEL, SLES, and Debian. Also The policy for RHEL and Debian are named differently (RHEL = targeted) and
(Debian = default), I currently don't know what the poilicy for SLES is
named. Also, I need to register set_selinux and task_result for this
because if I don't register them my task doesn't work.

You have not explained why, "doesn't work" is not an explanation.

You can only use one register on a task, if you have several only the last one is set.


I'm still quite new
to Ansible so some things are still confusing. I don't understand the
set_fact task!!!! Here is my selinux.yaml:

---
- name: install selinux dependencies when selinux is installed on Debian
  apt:
    name: ['policycoreutils', 'checkpolicy', 'selinux-basics',
'python-selinux' ]
    state: present
  when: ansible_distribution|lower == 'debian'
- name: Set SELinux to permissive mode | RHEL
  selinux:
    policy: targeted
    state: permissive
  register: set_selinux
  register: task_result
  when: ansible_distribution|lower == 'redhat'
- name: Set SELinux to permissive mode | Debian
  selinux:
    policy: default
    state: permissive
  register: set_selinux
  register: task_result
  when:
    - ansible_selinux_python_present|bool
    - ansible_distribution|lower == 'debian'
- name: Reboot the server and wait for it to come back up.
  reboot:
  when: task_result is changed

Here you are reusing the same variable in register, that will not work since it will be overwritten by the last task.

--
Kai Stian Olstad

--
You received this message because you are subscribed to the Google Groups "Ansible 
Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/ba2cdb54787bb21e8f6de337dc106f7e%40olstad.com.

Reply via email to