Bug #595
puppet choke on non english LANG settings
| Status: | Closed | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | % Done: | 0% |
||
| Category: | - | |||
| Target version: | - | |||
| Affected Puppet version: | 0.25.4 | Branch: | ||
| Keywords: | ||||
| Votes: | 0 |
Description
i got a little idea there,
should not puppet use environement LANG=C when managing facts or packages etc… ?
i have LANG=fr_FR.UTF-8
and puppet choke on quite a few facts (erors messages with uname for exemple: Pour en savoir davantage, faites: « uname —help ». ) and also with packages updates :
/usr/bin/apt-cache policy mysql-client-4.1 => err: Packagemysql-client-4.1: Could not find latest version err: Packagemysql-client-4.1: Could not find latest version err: Packagemysql-client-4.1: Could not find latest version
just fails in puppet but works on command line.
when doing setenv LANG C it then works. What do you think ?
regards, Ghislain.
History
Updated by Benjamin Kite about 5 years ago
Setting LANG=C should take care of it until we internationalize/localize.
Updated by David Schmitt about 5 years ago
This has nothing to do with puppet’s i18n/l10n. As long as puppet has to parse some command output, LANG should be set to C for each call to avoid such surprises.
Updated by Matt Palmer about 5 years ago
- Status changed from 1 to 2
I think this is a fantastic idea. The best place to put the env change would probably be in the exec/system wrapper(s) that everything does/should use. As Russ Allbery noted, though, I think it should be LC_ALL=C rather than LANG=C, although going nuts and setting both of them might be an idea (I vaguely recall some apps that only looked at LANG).
Updated by Matt Palmer about 5 years ago
- Status changed from 2 to Closed
- 7 set to fixed
Fixed in r2456.