-
Notifications
You must be signed in to change notification settings - Fork 314
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 netaddr #129
Comments
Hi, Thanks for using the role and reporting this. It will be fixed shortly. |
This is now fixed in v1.29.0 |
FYI when using a virtualenv as one might with something like Molecule, this will cause the role to fail:
|
- Add performance tuning configuration (thanks @t0k4rt) - Update documentation - Conditionally install Python dependency baed on virtualenv or --user Addresses #129 (comment)
Hey @gaahrdner! Thanks for the heads up! I fixed this with a conditional |
- Add performance tuning configuration (thanks @t0k4rt) - Set raft multiplier to 1 - Conditionally install Python dependency baed on virtualenv or --user Addresses #129 (comment) - Update includes to import_tasks and include_tasks - Remove invalid consul_version key from configuration - Update Vagrantfile - Set client address to 0.0.0.0 so Vagrant based deploy checks now pass - Update documentation
Hi, just a question for my understanding, why do we need to install something on our workstation? My playbook fail because of this first task, becase I created a playbook that use a dedicated sudo user with |
Ok it is used by the local controller machine to be able to use the filter |
Yes, it's just a convenience thing that was added to deal with IPs |
It is not usable with a playbook that use sudo with password. Beause the sudo password is never the same between our workstation and target servers |
I agree with @Sispheor that we should not install stuff on the local machine by default. Using an opt-in flag could be a good middle ground. (Never really liked this) |
Agree that it's less than ideal. If the IP handling can be done without it, I'd be happy to see it removed. |
Does anyone want to work on making the role work without netaddr? |
this only supports ipv4 addresses, i don't know if the client address can even be ipv6 but please confirm if so addresses issue 129: ansible-collections#129
The first task generates an error on my environment (minimal Debian)
The pip package netaddr was not installed and using the flag "become: false" generate a failure due of the permission.
I had to add the option "extra_args: --user" in order to make it work.
pip:
name: netaddr
extra_args: --user
delegate_to: 127.0.0.1
become: false
The text was updated successfully, but these errors were encountered: