Ansible Reboot Error...

35 views
Skip to first unread message

kmarty009

unread,
Mar 31, 2020, 3:11:14 PM3/31/20
to Ansible Project
I get this error when executing my playbook.  I need to reboot the machine but cannot get around this insane error that is preventing me from doing so.. the plybook works until I add the last line for reboot.  Can anyone tell me what is wrong here please???  Thanks in advance.  

**** ERROR SECTION*****

ERROR! no action detected in task. This often indicates a misspelled module name, or incorrect module path.

The error appears to have been in '/home/kmarty/ansible/roles/basic/tasks/main.yml': line 53, column 3, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:


- name: Reboot Machine
  ^ here


The error appears to have been in '/home/kmarty/ansible/roles/basic/tasks/main.yml': line 53, column 3, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:


- name: Reboot Machine
  ^ here

exception type: <class 'ansible.errors.AnsibleParserError'>
exception: no action detected in task. This often indicates a misspelled module name, or incorrect module path.

The error appears to have been in '/home/kmarty/ansible/roles/basic/tasks/main.yml': line 53, column 3, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:


- name: Reboot Machine
  ^ here

**** PLAYBOOK******


#Ansible Configuration Playbook for On-Premise Installs
#Created by: Kirk Marty kmar...@gmail.com
#Version 1.0 
#Date: 3/31/2020

- name: "Required Software Packages that will be utilized - yum installs"
  yum: pkg={{ item }} state=installed
  with_items:
  - nano
  - vim
  - tar
  - xz
  - unzip
  - wget
  - curl
  - bind-utils
  - net-tools
  - ntp
  - epel-release

# Update the system to latest patches and applications via yum

- name: "update the Centos Server 7 with latest patches and applications"
  yum:
    name: "*"
    state: latest

- name: be sure firewalld is installed
  yum: name=firewalld state=installed
  tags:
   - install
   - firewalld
 
- name: be sure firewalld is disabled
  systemd: name=firewalld enabled=no
  tags:
   - install
   - atomic
   - firewalld

- name: be sure firewalld is stopped
  systemd: name=firewalld state=stopped
  ignore_errors: yes
  tags:
   - install
   - atomic
   - firewalld

- name: Disable SELinux
  selinux:
    state: disabled

- name: Reboot Server to apply some changes and updates
  reboot:

Dick Visser

unread,
Mar 31, 2020, 4:22:35 PM3/31/20
to ansible...@googlegroups.com
This usually means that the ansible version you use does not know that module.
According to https://docs.ansible.com/ansible/latest/modules/reboot_module.html
the reboot module was introduced in 2.7.
This indicates you're using something older.

What is the output of 'ansible --version'?
> --
> 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-proje...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/8ef94b84-40cd-4105-857b-f82a6787d89a%40googlegroups.com.



--
Dick Visser
Trust & Identity Service Operations Manager
GÉANT

Jordan Borean

unread,
Mar 31, 2020, 4:24:32 PM3/31/20
to Ansible Project
It’s telling you it cannot find the reboot module/plugin. Make sure you are on Ansible 2.7 or higher as that is when the module was added https://docs.ansible.com/ansible/latest/modules/reboot_module.html,

kmarty009

unread,
Mar 31, 2020, 8:02:01 PM3/31/20
to Ansible Project
Interesting!  Thanks for the responses!  I really appreciate it.  

I'm new to ansible and trying to get into a love affair with it.  I'm running CentOS 7.7.1908 and Ansible 2.4.2.0 was installed.  

I did a yum install epel-release and I got installed new version at 2.9.6  

Of course, that worked and rebooted my machine!  However, I did run into new issues with DEPRECATION WARNING.  I think it's not liking the state=installed.  If I'm reading the manual (RTFM) it wants a newer flag of state=present.  

I also don't think it's loving the {{ item }} flag and wants something different.  {{ packages }}?  

[DEPRECATION WARNING]: Invoking "yum" only once while using a loop via squash_actions is deprecated. Instead of using a loop to supply
multiple items and specifying `pkg: "{{ item }}"`, please use `pkg: ['nano', 'vim', 'tar', 'xz', 'unzip', 'wget', 'curl', 'bind-utils', 'net-
tools', 'ntp', 'epel-release']` and remove the loop. This feature will be removed in version 2.11. Deprecation warnings can be disabled by
setting deprecation_warnings=False in ansible.cfg.
[DEPRECATION WARNING]: Invoking "yum" only once while using a loop via squash_actions is deprecated. Instead of using a loop to supply
multiple items and specifying `pkg: "{{ item }}"`, please use `pkg: ['nano', 'vim', 'tar', 'xz', 'unzip', 'wget', 'curl', 'bind-utils', 'net-
tools', 'ntp', 'epel-release']` and remove the loop. This feature will be removed in version 2.11. Deprecation warnings can be disabled by
setting deprecation_warnings=False in ansible.cfg.

> To unsubscribe from this group and stop receiving emails from it, send an email to ansible...@googlegroups.com.

kmarty009

unread,
Mar 31, 2020, 8:23:16 PM3/31/20
to Ansible Project
I got it all working.  I had to update the hosts, file and use new syntax that was outlined in the documentation.  Thanks everyone, I'm all good!  
Reply all
Reply to author
Forward
0 new messages