-
-
Notifications
You must be signed in to change notification settings - Fork 115
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
Failing on MacOS (Catalina) as control machine #115
Comments
Hi, I have merged PR #135 that would fix this issue. Kind regards, |
Hi Werner. Not yet I'm afraid.
I'm testing against master branch code. Should I try another one? Cheers, |
Hi @bengoa Can you provide that version you have configured with the property Kind regards, |
Hi Werner. I have been using '*' as my telegraf_agent_version to avoid unwanted upgrades:
Maybe there's a better way to do that? Cheers,
|
Hi @bengoa The property needs a valid version if you want to not upgrade. The Kind regards, |
Hi Werner. Let me give it a try. I remember in the past (2 years ago) of having packages being upgraded/downgraded to the version set to telegraf_agent_version. Cheers.
|
Hi Werner. I made a test here setting the parameters like this:
If I ran against a server with version 1.15.3-1 installed, it tries to downgrade to 1.10.0:
I have a heterogeneous environment here, running CentOSes from 6 to 8 and Debians 9 and 10. Using '*' doesn't enforce the downgrade/upgrade to the version set at telegraf_agent_version and I'm able to keep a single vars files for all these operating systems versions ensuring a consistent deploy. Maybe telegraf_agent_package_state is being ignored? Cheers, |
Hi Alberto, Ah yes, it seems that the version is part of the package name and thus it sees that it isn't installed. Kind regards, |
Describe the bug
When running this role from a MacOS (Catalina) it is failing with this error:
Installation method/version
Ansible Version
_
Targetted hosts
Concerns the following OS(es):
Expected behavior
Shouldn't be failing
Additional context
It is failing with Ansible 2.8 @ Catalina as well. I'm not 100% positive, but I guess it may be related to the Python version (3.x) instead of Ansible itself.
I have another machine running Linux and Ansible 2.8/2.9 and it works fine with Python 2.7.
The text was updated successfully, but these errors were encountered: