ibm-spectrum-scale-install-infra icon indicating copy to clipboard operation
ibm-spectrum-scale-install-infra copied to clipboard

Check that Ansible playbooks run on different LANGUAGE settings

Open mrolyat opened this issue 4 years ago • 0 comments

Several field issues were encountered with existing install toolkit where the server was running in a different language. Opening an issue to run a few tests to ensure Ansible can handle the different languages and still run successfully.

This was typically corrected by: 1 ) AFAIK, the export command is supported in all flavors of Linux (RH, Ubuntu, SUSE) and AIX.

2 ) Well, I usually use UTF-8 and works well for most of application. I faced a situation where a client was using en_US and the msgs was only showing properly when using UTF-8. I found this explanation that guides me to adopt en_US.UTF-8 rather than en_US.

The only difference between en_US and en_US.UTF8 is that the former uses ISO-8859-1 for a character set, while the latter uses UTF-8. Prefer UTF-8. The only difference in these is in what characters they are capable of representing. ISO-8859-1 represents characters common to many Americans (the English alphabet, plus a few letters with accents), whereas UTF-8 encodes all of Unicode, and thus, just about any language you can think of. UTF-8, today, is a defacto standard encoding for text.

https://www.ibm.com/support/knowledgecenter/STXKQY_5.0.4/com.ibm.spectrum.scale.v5r04.doc/bl1ins_preparingtousetoolkit.htm

https://www.ibm.com/support/knowledgecenter/STXKQY_5.0.4/com.ibm.spectrum.scale.v5r04.doc/bl1ins_limitationsofthetoolkit.htm

Non-English languages in client programs such as PuTTY The installation toolkit does not support setting the language in client programs such as PuTTY to any language other than English. Set the language of your client program to English.

note

locale_gen:
name: en_US.UTF-8
state: present
- name: set as default locale
command: localectl set-locale LANG=en_US

mrolyat avatar Apr 07 '20 18:04 mrolyat