Skip to content
This repository has been archived by the owner on Feb 13, 2023. It is now read-only.

Possible syntax problem in solr role. #1018

Closed
TipiT opened this issue Nov 27, 2016 · 4 comments
Closed

Possible syntax problem in solr role. #1018

TipiT opened this issue Nov 27, 2016 · 4 comments
Labels

Comments

@TipiT
Copy link

TipiT commented Nov 27, 2016

Issue Type

  • Bug Report / Support Request

Your Environment

Vagrant 1.8.6
VirtualBox 5.1.8r111374
ansible 2.1.2.0
  config file = /etc/ansible/ansible.cfg
  configured module search path = Default w/o overrides

Your OS

  • Linux Ubuntu 15.10 wily

Full console output

vagrant up --provision

statically included: drupal-vm/provisioning/roles/geerlingguy.solr/tasks/install.yml
ERROR! no action detected in task. This often indicates a misspelled module name, or incorrect module path.

The error appears to have been in 'drupal-vm/provisioning/roles/geerlingguy.solr/tasks/install.yml': line 27, column 3, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:

  • name: Run systemd daemon_reload (RHEL 7 workaround).
    ^ here

The error appears to have been in 'drupal-vm/provisioning/roles/geerlingguy.solr/tasks/install.yml': line 27, column 3, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:

  • name: Run systemd daemon_reload (RHEL 7 workaround).
    ^ here

Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.

Summary

I just can't seem to figure out what is the exact syntax problem is here or why it even affects my provisioning because I don't use RedHat distro.

So of course the solution was to comment out the these two plays.

This appeared when I pulled to commit: da79ab7

@geerlingguy
Copy link
Owner

@TipiT - Can you upgrade to Ansible 2.2.x? Otherwise the daemon_reload configuration in the solr role's latest version won't work.

@geerlingguy
Copy link
Owner

Also pushed up a change that I'll test to bump the minimum Ansible requirement; sorry for missing that!

@TipiT
Copy link
Author

TipiT commented Nov 28, 2016

Upgrading to (latest) ansible 2.2.0.0 did the trick. Thank you for the quick help!

@geerlingguy
Copy link
Owner

@TipiT - Thanks for the bug report :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants