Project

Profile

Help

Issue #6434

closed

ansible-pulp does not ensure that a full Unicode locale is installed

Added by mdepaulo@redhat.com almost 4 years ago. Updated over 3 years ago.

Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Category:
Installer - Moved to GitHub issues
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
1. Low
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

Per the pulp-dev email thread "Language pack on Fedora":

Hey guys,

On Fedora, (now presumably EL8 as well), we get lots of warnings/errors (including within the postgreql ansible role I think), unless we install the en_US.UTF-8 locale (to replace/supplement the C.UTF-8 locale) via the package "glibc-langpack-en".

It became an issue for us on either Fedora 29 or 30, which split this into a subpackage, and do not default to installing en_US.UTF-8 in container images. (For Fedora's minimization efforts.)

For now, we are just installing the package.

Does anyone know if Pulp / postgres actually needs it? In the long term, should we either require en_US.UTF-8, or fix the warnings?

Reference info below.

-Mike

The kickstart that generates the F30 container images, search for "LANG".

https://fedoraproject.org/wiki/Changes/python3_c.utf-8_locale

The answer via conversations was that Pulp might need it since we interpret metadata like RPM changelogs containing unicode chars for peoples' names.

For postgres, we'd have to research more.

It is currently installed in the pulp/pulpcore operator-centric container image (Fedora 30), but not in guaranteed to be installed by ansible-pulp. It actually is in the Dockerfile for molecule for Fedora & CentOS 8.

Also available in: Atom PDF