Closed rreilly-edr closed 7 years ago
That's strange!
Can you run ansible localhost -m setup -a 'filter=ansible_distribution'
on the host and paste the output here?
I will this is in a packer pipeline, need to spin one up and run the test, I will do this asap
Hi here is the output
localhost | SUCCESS => {
"ansible_facts": {
"ansible_distribution": "Ubuntu"
},
"changed": false,
"failed": false
}
What kind of AMI is this? I'll try to reproduce it.
ami-1d4e7a66
now i cannot find that image.. but it was generic ubuntu 16.04
I'll take a look tomorrow!
So I just tried to replicate this issue, using the same AMI as you on AWS. However for me it worked. Is it possible that you provide your FULL playbook, so I can try to reproduce it?
I will need to check, I did not write it and need to make sure there is nothing i need to redact.
I just ran into this, and I figured out the problem. If you're like me, you just did an "apt install ansible" but that installs ansible 2.0.0. This needs 2.2.1 or higher.
hmm, i think i did a pip install ansible but i will double check that ! thanks
Yep it looks like the person who wrote the packer files used a bash script to install ansible from apt-get :( ok i will fix this to install from pip. thank you so much, i will report back
I checked the readme and meta-files and they already mention minimum ansible version 2.2.1., so I'm closing this now.
If you need further help, feel free to reopen!
Hi, when running the hardening against ubuntu 16.04 I get the below error, seems to think it is rhel ?