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

PIP dependencies conflicting with native yum packages #28

Closed
christopherobin opened this issue Feb 27, 2017 · 1 comment
Closed

PIP dependencies conflicting with native yum packages #28

christopherobin opened this issue Feb 27, 2017 · 1 comment

Comments

@christopherobin
Copy link

For the RedHat version the playbook installs a bunch of pip dependencies which, as far as I can see, are only used by tests (since Telegraf is written in go).

Those dependencies are causing issues with packages that might actually depend for example on the python-urllib3 yum package since yum will fail if files installed by the package already exist on the system.

Would it be possible to remove those dependencies? Or at least move them to the test.yml test playbook?

@dj-wasabi
Copy link
Owner

Hi @christopherobin

Yes, the role should only install packages needed for correct usage of the application. If the pip packages are only used for testing, then it should be removed from the role and places in the playbook.yml.

tszym added a commit to tszym/ansible-telegraf that referenced this issue Oct 17, 2017
Once used for testing, these packages are no longer useful and can even
lead to certain issues, as installation can fail.
tszym added a commit to tszym/ansible-telegraf that referenced this issue Oct 17, 2017
Once used for testing, these packages are no longer useful and can even
lead to certain issues, as installation can fail.
tszym added a commit to tszym/ansible-telegraf that referenced this issue Oct 18, 2017
Once used for testing, these packages are no longer useful and can even
lead to certain issues, as installation can fail.
dj-wasabi added a commit that referenced this issue Oct 18, 2017
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

2 participants