We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
If I include the following in Hiera:
nginx::nginx_upstreams: 'mycluster': ensure: 'present' members: [ '192.168.0.1:80', '192.168.0.2:80' ] upstream_cfg_prepend: ip_hash: ''
The file that is created simply adds a blank line instead of the expected ip_hash line. As discussed in this Google Groups post the consensus seems to be an issue in the template: https://groups.google.com/forum/#!topic/puppet-users/tE3fRJaLU3A
I have tried this on two CentOS 6 environments with v0.0.10 & v0.2.2 of the module to the same effect.
The text was updated successfully, but these errors were encountered:
FWIW, with the current version, I get (with that hiera config)
# MANAGED BY PUPPET upstream mycluster { ip_hash ; server 192.168.0.1:80 fail_timeout=10s; server 192.168.0.2:80 fail_timeout=10s; }
However, I don't think the template or manifest has changed since 5829559 e0843af
so not sure. @kemra102: are you able to reproduce this still, or is it still a problem for you?
Sorry, something went wrong.
@wyardley I no longer have access to a system running this so not able to test.
Ok, I'm going to close this for now, please open a new ticket or re-open if you (or someone else) reproduce this with a current release.
No branches or pull requests
If I include the following in Hiera:
The file that is created simply adds a blank line instead of the expected ip_hash line. As discussed in this Google Groups post the consensus seems to be an issue in the template: https://groups.google.com/forum/#!topic/puppet-users/tE3fRJaLU3A
I have tried this on two CentOS 6 environments with v0.0.10 & v0.2.2 of the module to the same effect.
The text was updated successfully, but these errors were encountered: