Since the failing code is running in mock you need the locale files in mock
and not on the list itself.

The package group we install in mock by default should include the needed
locales. If it doesn't, it looks like a packaging bug in CentOS.

בתאריך יום ב׳, 17 בדצמ׳ 2018, 11:32, מאת Evgheni Dereveanchin (oVirt JIRA) <

You're right, C.UTF-8 may be the issue here.
Looking at some bare metals, it is not installed:
$ locale -a | grep ^C
C

Need to dig deeper to confirm what is setting this locale and if it is related to Jenkins upgrades.
This seems to be shipped with Fedora glibc but our CentOS systems, even the newly built 7.6 ones don't have it.

LC_ALL is a catch-all override variable, you're not supposed to set it normally.

Since LANG is set by defaukt, it aught to be enough - I think the real issue is that LANG is set by default to a value we're missing the files for - so we need to ensure the files get installed.

It also may be linked to the behavior of certain applications. Specifically, I've seen this with virsh when working on OVIRT-2575:

ssh ovirt-srv18.phx.ovirt.org virsh list
X11 forwarding request failed on channel 0
setlocale: No such file or directory
Id Name State
----------------------------------------------------

However running other commands, such as "ls" does not produce this error

ssh ovirt-srv18.phx.ovirt.org ls -l
X11 forwarding request failed on channel 0
total 0

Digging further makes me think that the value of LC_ALL is causing the issue as it is empty in my env and passed via SSH like that. If I set it to C the setlocale warning goes away in virsh.

This is confirmed by other lines in the log:

11:23:18 perl: warning: Setting locale failed.
11:23:18 perl: warning: Please check that your locale settings:
11:23:18 LANGUAGE = (unset),
11:23:18 LC_ALL = (unset),
11:23:18 LANG = "C.UTF-8"
11:23:18 are supported and installed on your system.

what's the best way to define env vars in the build to set LANG, LC_ALL and LANGUAGE to C and get rid of these warnings?

I think this is specific to the node-ng build job that was linked to.

It seems to be trying to run the 'setlocale' command on multiple occasions and failing.

It looks like it can be a simple matter of installing the right package in the *. packages file.

Looking at my own RHEL workstation - I don't have the 'setlocale' command - so it may have been deprecated or move around at some point.

any idea what can cause it?