Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

claw-playbook: ERROR! 'debugger' is not a valid attribute for a Play #1293

Closed
t4k opened this issue Oct 7, 2019 · 9 comments
Closed

claw-playbook: ERROR! 'debugger' is not a valid attribute for a Play #1293

t4k opened this issue Oct 7, 2019 · 9 comments
Milestone

Comments

@t4k
Copy link

t4k commented Oct 7, 2019

Vagrant 2.2.3
Ansible 2.4.2.0

vagrant up

ERROR! 'debugger' is not a valid attribute for a Play

The error appears to have been in '/…/claw/solr.yml': line 3, column 3, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:

  • hosts: solr
    ^ here

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

I was able to get past the error by commenting out line 5 in solr.yaml:

  debugger: on_failed
@elizoller
Copy link
Member

i had the same error on vagrant 2.2.4 and ansible 2.8.3

@DonRichards
Copy link
Member

@t4k @elizoller Just looking at the documentation for Ansible 2.2 and I see it does support the debugger parameter so it should work. I wonder if it's failing because of something else failing. If you remove the line does it finish building?

@t4k
Copy link
Author

t4k commented Oct 8, 2019

Yes, everything worked perfectly with that single line commented out.

@t4k
Copy link
Author

t4k commented Oct 8, 2019

New in version 2.5.

The debugger keyword can be used on any block where you provide a name attribute, such as a play, role, block or task.

Looks like it requires Ansible 2.5 and a name attribute. There is no name attribute in this section of the file.

@t4k
Copy link
Author

t4k commented Oct 8, 2019

Maybe an Ansible compatibility_mode needs to be set in the Vagrantfile: https://www.vagrantup.com/docs/provisioning/ansible_common.html#compatibility_mode

@DonRichards
Copy link
Member

Interesting. I just created a PR for this.

@elizoller
Copy link
Member

Sorry, this might be a dumb question but why would we want to force it to behave like a previous version of vagrant? Isn't that what compatibility mode does?

@DonRichards
Copy link
Member

I believe so, that's how I read it.

@dannylamb
Copy link
Contributor

Are we good to close this one?

@dannylamb dannylamb added this to the 1.1.0 milestone Jan 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants