Bug 1366916
Summary: | [engine-setup] When SSHing to the engine machine form an OSX client engine-setup might fail due to locale settings | ||||||
---|---|---|---|---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Gil Klein <gklein> | ||||
Component: | Setup.Engine | Assignee: | Yedidyah Bar David <didi> | ||||
Status: | CLOSED WONTFIX | QA Contact: | Pavel Stehlik <pstehlik> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 4.0.2 | CC: | bugs, didi, gveitmic, mkalinin, ylavi | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2016-09-08 08:57:02 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | Integration | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Gil Klein
2016-08-14 20:23:14 UTC
Created attachment 1190775 [details]
ovirt engine setup log
A quick search for 'yum "unknown locale: UTF-8"' finds: http://stackoverflow.com/questions/19961239/pelican-3-3-pelican-quickstart-error-valueerror-unknown-locale-utf-8 https://bugs.python.org/issue18378 Can you please check your environment? If not sure please attach sosreport. (In reply to Yedidyah Bar David from comment #2) > A quick search for 'yum "unknown locale: UTF-8"' finds: > > http://stackoverflow.com/questions/19961239/pelican-3-3-pelican-quickstart- > error-valueerror-unknown-locale-utf-8 > https://bugs.python.org/issue18378 > > Can you please check your environment? If not sure please attach sosreport. Look like: export LC_ALL=en_US.UTF-8 solved it. I see that LC_ALL is not set even on other systems. Can we consider setting it to workaround this issue? (In reply to Gil Klein from comment #3) > (In reply to Yedidyah Bar David from comment #2) > > A quick search for 'yum "unknown locale: UTF-8"' finds: > > > > http://stackoverflow.com/questions/19961239/pelican-3-3-pelican-quickstart- > > error-valueerror-unknown-locale-utf-8 > > https://bugs.python.org/issue18378 > > > > Can you please check your environment? If not sure please attach sosreport. > Look like: export LC_ALL=en_US.UTF-8 solved it. In the shell where you ran engine-setup? What's the output of 'locale'? > > I see that LC_ALL is not set even on other systems. On my machine I don't have LC_ALL but do have LANG=en_US.UTF-8 . > > Can we consider setting it to workaround this issue? Yes. (In reply to Yedidyah Bar David from comment #4) > (In reply to Gil Klein from comment #3) > > (In reply to Yedidyah Bar David from comment #2) > > > A quick search for 'yum "unknown locale: UTF-8"' finds: > > > > > > http://stackoverflow.com/questions/19961239/pelican-3-3-pelican-quickstart- > > > error-valueerror-unknown-locale-utf-8 > > > https://bugs.python.org/issue18378 > > > > > > Can you please check your environment? If not sure please attach sosreport. > > Look like: export LC_ALL=en_US.UTF-8 solved it. > > In the shell where you ran engine-setup? Yes, if I set it on the same shell, I was able to continue with the setup process. > > What's the output of 'locale'? # locale locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory LANG=en_US.UTF-8 LC_CTYPE=UTF-8 LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= > > > > > I see that LC_ALL is not set even on other systems. > > On my machine I don't have LC_ALL but do have LANG=en_US.UTF-8 . > > > > > Can we consider setting it to workaround this issue? > > Yes. (In reply to Gil Klein from comment #5) > (In reply to Yedidyah Bar David from comment #4) > > What's the output of 'locale'? > # locale > locale: Cannot set LC_CTYPE to default locale: No such file or directory > locale: Cannot set LC_ALL to default locale: No such file or directory > LANG=en_US.UTF-8 > LC_CTYPE=UTF-8 Perhaps this one is causing this. What do you have in /etc/sysconfig/i18n ? and in /root/.i18n ? (In reply to Yedidyah Bar David from comment #6) > (In reply to Gil Klein from comment #5) > > (In reply to Yedidyah Bar David from comment #4) > > > What's the output of 'locale'? > > # locale > > locale: Cannot set LC_CTYPE to default locale: No such file or directory > > locale: Cannot set LC_ALL to default locale: No such file or directory > > LANG=en_US.UTF-8 > > LC_CTYPE=UTF-8 > > Perhaps this one is causing this. > > What do you have in /etc/sysconfig/i18n ? and in /root/.i18n ? # ls -l /etc/sysconfig/i18n ls: cannot access /etc/sysconfig/i18n: No such file or directory # ls -l /root/.i18n ls: cannot access /root/.i18n: No such file or directory (In reply to Gil Klein from comment #7) > (In reply to Yedidyah Bar David from comment #6) > > (In reply to Gil Klein from comment #5) > > > (In reply to Yedidyah Bar David from comment #4) > > > > What's the output of 'locale'? > > > # locale > > > locale: Cannot set LC_CTYPE to default locale: No such file or directory > > > locale: Cannot set LC_ALL to default locale: No such file or directory > > > LANG=en_US.UTF-8 > > > LC_CTYPE=UTF-8 > > > > Perhaps this one is causing this. > > > > What do you have in /etc/sysconfig/i18n ? and in /root/.i18n ? > # ls -l /etc/sysconfig/i18n > ls: cannot access /etc/sysconfig/i18n: No such file or directory That's normally created during installation, should always exist imo. If you ssh to this machine from another one, can also be set in the client - you can check with 'ssh -v', and/or 'ssh -F /dev/null'. Perhaps you ssh from a Mac [1]? I'd close this bug. If you want to keep it, should probably be set on otopi, to emit a warning or error if locale seems wrong. Not sure it's worth it though - mis-configured locale probably causes many other problems. [1] http://www.cyberciti.biz/faq/os-x-terminal-bash-warning-setlocale-lc_ctype-cannot-change-locale/ (In reply to Yedidyah Bar David from comment #8) > (In reply to Gil Klein from comment #7) > > (In reply to Yedidyah Bar David from comment #6) > > > (In reply to Gil Klein from comment #5) > > > > (In reply to Yedidyah Bar David from comment #4) > > > > > What's the output of 'locale'? > > > > # locale > > > > locale: Cannot set LC_CTYPE to default locale: No such file or directory > > > > locale: Cannot set LC_ALL to default locale: No such file or directory > > > > LANG=en_US.UTF-8 > > > > LC_CTYPE=UTF-8 > > > > > > Perhaps this one is causing this. > > > > > > What do you have in /etc/sysconfig/i18n ? and in /root/.i18n ? > > # ls -l /etc/sysconfig/i18n > > ls: cannot access /etc/sysconfig/i18n: No such file or directory > > That's normally created during installation, should always exist imo. > > If you ssh to this machine from another one, can also be set in the client - > you can check with 'ssh -v', and/or 'ssh -F /dev/null'. Perhaps you ssh from > a Mac [1]? You got it right, I opened the SSH session from an OSX machine. I can confirm the suggested workaroud solved this issue. > > I'd close this bug. If you want to keep it, should probably be set on otopi, > to emit a warning or error if locale seems wrong. Not sure it's worth it > though - mis-configured locale probably causes many other problems. Two suggestions here: 1. Can we detect this issue and send OSX users a reference to the suggested workaround? 2. I would suggested adding a documention / kb article to help unblock OSX users from running engine-setup > > [1] > http://www.cyberciti.biz/faq/os-x-terminal-bash-warning-setlocale-lc_ctype- > cannot-change-locale/ Please open a bug on freebsd. Can you create a KB? (In reply to Yaniv Dary from comment #10) > Please open a bug on freebsd. > Can you create a KB? I'm not sure how to create a KB article. Marina, can you please assist? Thanks, Germano, for the KCS: https://access.redhat.com/solutions/2790341 See also bug 1670376. |