-
Notifications
You must be signed in to change notification settings - Fork 571
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
Fails due to incorrect locale #110
Comments
I'm going to try and get a travis run using your locale and see if I can get a failing test case... ...The tests are passing, though this may be because Ive not got the right setup in travis... will tweak it a little to try and get a failure condition |
do you have |
Yes I have postgresql_locale: 'en_AU.UTF-8' set in my playbook but didn't have postgresql_lc_* set. They defaulted to en_US.UTF-8. Having changed them explicitly the failing step is working.
I don't seem to have a /var/lib/locales/supported.d/local file, infact /var/lib/locales doesn't exist on this system.
|
Are you happy to close this issue? I have added a section to the README to make it clear on how to change locale.. see #112 .. update: changed the focus of the change to make local changing easier by setting |
After reading #112 I'm happy for this to be closed. |
Hi,
My DB is failing to start due to some invalid configuration entries
Seems this is due to the system locale differing from the strings being complained about (I have postgresql_locale: 'en_AU.UTF-8' set).
I think the best solution would be to the relevant lc_* entries so they default to postgresql_locale if not set specifically.
I believe http://docs.ansible.com/ansible/playbooks_filters.html#defaulting-undefined-variables is the relevant part of the docs.
The text was updated successfully, but these errors were encountered: