-
-
Notifications
You must be signed in to change notification settings - Fork 8
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
Role setting remote locale to same as local locale instead of var defined one #3
Comments
It's not easy to verify ( I have tried to verify better however. For your playbook, where does the |
This is probably set to
As I explained above, my notebook is set to this locale. As you suspected, I checked and noticed my ssh config is indeed forwarding the local locale. The server is configured to accept it. Are you suggesting to either disable reception on the server side or forwarding on my local machine and try again? The overall behavior is weird though, as none of the related configs changed over time. The only thing that changed is that I updated ansible (to core 2.11.3) and the role to its most recent version (3.1.0). That's when the play broke and I started to see the reported behavior. That is why I suspected changes within ansible to be responsible, allthough I was unable to verify that (yet). |
I guess I owe you an apology for bothering you again with issues that aren't actual issues. I just rechecked all locale related settings to make absolutely sure I wasn't misinterpreting something, but appearently I was. 🤦♂️ Your hint about ssh accepting the LC_* from the host logging pointed me to the curlprit. The servers default locale was always properly set to the value defined by I'm still wondering though, why I didn't see this behavior before the above mentioned updates of ansible and the role. 🤔 I'll close the issue with a big thank you for taking your time helping me figuring out my (stupid) mistakes! 😅 I'll also open up a pull request adding information about this behavior to your readme, hoping it will prevent others from facing the same "problem". |
As described within the issue robertdebock#3 I'd like to add hints about this SSH behavior to the readme.
Don't worry, I learn from these kinds of issues too. So far; your issue are certainly interesting. Thanks for following up! |
Describe the bug
The role sets the remote machine to the same locale as the machine running ansible, instead of using var defined values. This seems weird, as the role performs no checks regarding the local locales, only the asertions are delegated to localhost, but that shouldn't impact values within vars. Is it possible there is some sort of variable collision (ansible magic var <> locale_lang)?
Playbook
See this issue for my playbook.
Output
I'll just paste the additional (verbose) output not shown in the above mentioned issue. Note that I am provisioning 2 hosts with this role, I just censored the actual domains of those servers, thats why you can see two
ok: [my.remote.host] ...
statements each. Also this was the second run of the play using the role, thats why there appear nochanged
statements.This is what the server says after the role ran:
Before it was all set to
C.UTF-8
which appears to be the default value within a proxmox ubuntu 20.04 container.Environment
See this issue for my environment.
The text was updated successfully, but these errors were encountered: