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

behavior with fact script #13

Open
stefangweichinger opened this issue Mar 17, 2021 · 0 comments
Open

behavior with fact script #13

stefangweichinger opened this issue Mar 17, 2021 · 0 comments

Comments

@stefangweichinger
Copy link

In my small role https://github.com/stefangweichinger/ansible-rclone I use your images to run molecule tests.

In this issue stefangweichinger/ansible-rclone#80 and the resulting PR stefangweichinger/ansible-rclone#82 I added a check script template:

https://github.com/stefangweichinger/ansible-rclone/blob/master/templates/etc/ansible/facts.d/rclone.fact.j2

It should check if the binary exists and report back the variable "ansible_facts.ansible_local.rclone.installed".

In the ansible/molecule runs that variable is always "false" for the centos7 instances (at the 2nd run, sure, when the binary is there already), but when I login to the same instance and run the fact-script the variable is "true":

[root@instance-centos7 /]# /etc/ansible/facts.d/rclone.fact 
{
    "configured": true, 
    "installed": true, 
    "installed_version": "1.54.1"
}

Do you know the reason, did you see such a behavior as well?

I also tested your tag "python3", same behavior.

Maybe you have an idea here, thanks.

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

1 participant