Project

General

Profile

Actions

Bug #13496

open

foreman-installer error when locale is not en_US.utf8

Added by Grégoire Bellon-Gervais almost 9 years ago. Updated over 8 years ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
Foreman modules
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Hello,

I'm under debian 8 and my locales are set to en_GB.UTF-8.
I have followed the debian dedicated documentation, I just add the repositories and I install 'foreman-installer', then I execute the command :

foreman-installer

Then, I got the following errors :

 /Stage[main]/Foreman::Database::Postgresql/Postgresql::Server::Db[foreman]/Postgresql::Server::Database[foreman]/Exec[/usr/lib/postgresql/9.4/bin/createdb --port='5432' --owner='foreman' --template=template0 --encoding 'utf8' --locale=en_US.utf8  'foreman']: Failed to call refresh: /usr/lib/postgresql/9.4/bin/createdb --port='5432' --owner='foreman' --template=template0 --encoding 'utf8' --locale=en_US.utf8  'foreman' returned 1 instead of one of [0]

In postgresl error log, we can see this error :

2016-02-01 12:10:49 CET [4258-1] postgres@postgres ERROR:  invalid locale name: "en_US.utf8" 

Just adding locale 'en_US.utf8' using the command :

dpkg-reconfigure locales

And selecting "en_US.UTF-8 UTF-8" in the first screen "Locales to be generated" do the trick.

Thanks for your great tool.


Related issues 1 (0 open1 closed)

Related to Installer - Bug #11681: foreman, candlepin, gutterball databases use default encoding vs explicit UTF8ClosedIvan Necas09/03/2015Actions
Actions #1

Updated by Dominic Cleal almost 9 years ago

  • Tracker changed from Support to Bug
  • Project changed from Foreman to Installer
  • Category changed from Internationalization to Foreman modules
Actions #2

Updated by Dominic Cleal almost 9 years ago

  • Related to Bug #11681: foreman, candlepin, gutterball databases use default encoding vs explicit UTF8 added
Actions #3

Updated by Dominic Cleal over 8 years ago

  • Translation missing: en.field_release set to 123
Actions #4

Updated by Anonymous over 8 years ago

I'm a bit unsure what to do here. We could check the presence of that locale in a pre-hook, but probably that's also an issue for remote DB setups, so it might be just best to document that?

Actions #5

Updated by Ewoud Kohl van Wijngaarden over 8 years ago

I think we should do both.

Actions #6

Updated by Dominic Cleal over 8 years ago

Yeah, probably both. We could also perhaps have a fact to detect a non-en_US UTF-8 locale as a fallback?

Actions #7

Updated by Ewoud Kohl van Wijngaarden over 8 years ago

I can't judge how well non-en_US UTF-8 locales would work or if it may introduce subtle bugs. With en_GB that's unlikely, but for others I don't what it would do.

Actions #8

Updated by Grégoire Bellon-Gervais over 8 years ago

If you need, I can perform some tests with "exotic" locales.

Actions #9

Updated by Dominic Cleal over 8 years ago

  • Translation missing: en.field_release changed from 123 to 145
Actions #10

Updated by Anonymous over 8 years ago

  • Pull request https://github.com/theforeman/puppet-foreman/pull/417 added

I added a sentence to the theforeman-foreman readme, maybe this also should go to the quickstart/installer docs? As said, as I think this is mainly about the locale being available at the database node and it must be checked there I think it doesn't make sense to check in an installer hook.

Actions #11

Updated by Dominic Cleal over 8 years ago

  • Translation missing: en.field_release deleted (145)
Actions

Also available in: Atom PDF