'Failed to set locale, defaulting to C' for CentOS images on master

[Mark Goddard]

We see the following error when building CentOS images on master:

Failed to set locale, defaulting to C

Not seen if we remove this line from the base Dockerfile:

ENV LANG C.UTF-8

[Radosław Piliszek (yoctozepto)]

Hmm, indeed it was set for Ubuntu's/Debian's newer Python.
It looks supported in RHEL 8 though.

We can go en_US.UTF-8 and test if it passes our CI.
C.UTF-8 seems to have broken collation (sorting and comparing of Unicode).

As previously discussed, official Python images [1] use C.UTF-8 but they use Debian and Alpine (and Windows).

One thing is sure, we should not drop Unicode from images as this fixed Glance metadata errors we had.

[1] https://hub.docker.com/_/python

[Marcin Juszkiewicz (hrw)]

There is a bug https://bugzilla.redhat.com/show_bug.cgi?id=1361965 for adding C.UTF-8 to RHEL 7.

[Marcin Juszkiewicz (hrw)]

Looks like en_US.UTF-8 is a way to go. RHEL 7 will not get C.UTF-8 support.

From bugzilla:

"Given that RHEL 7 is entering maintenance phase 1 at the end of 2019, and this issue doesn't have upstream resolution yet, I'm moving to RHEL 8.0. In RHEL 8.0 we inherited the C.UTF-8 locale from Fedora and this needs fixing. We should fix the code-point issue at a minimum."

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/691835

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/691835
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=e910ef6cf67fcdb718823fbe06becc160e453e69
Submitter: Zuul
Branch: master

commit e910ef6cf67fcdb718823fbe06becc160e453e69
Author: Marcin Juszkiewicz <email address hidden>
Date: Tue Oct 29 11:11:31 2019 +0100

    base: use en_US.UTF-8 locale on all distros

    C.UTF-8 is not supported in RHEL 7:

    https://bugzilla.redhat.com/show_bug.cgi?id=1361965

    Closes-bug: #1850035
    Change-Id: I20dcb86e7e119b9f5ca44cd066fcb9cb84af1ce4

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/kolla 9.0.0.0rc1 release candidate.