Bug 1176457 – Can not restore backup file to rhevm with non-default lc_messages

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1176457 - Can not restore backup file to rhevm with non-default lc_messages

Summary:	Can not restore backup file to rhevm with non-default lc_messages

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Virtualization Manager
Classification:	Red Hat
Component:	ovirt-engine (Show other bugs)
Sub Component:
Version:	3.4.2
Hardware:	Unspecified Unspecified

Priority	high Severity high
Target Milestone:	ovirt-3.6.0-rc
Target Release:	3.6.0
Assigned To:	Yedidyah Bar David
QA Contact:	Jiri Belka
Docs Contact:

URL:
Whiteboard:
Keywords:	ZStream

Depends On:
Blocks:	1078871 1192954
	Show dependency tree / graph

Reported:	2014-12-21 19:56 EST by Yoshinori Takahashi
Modified:	2018-05-02 03:51 EDT (History)
CC List:	19 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:	Previously, lc_messages was sometimes set to a non-English locale in postgresql.conf. As a result, engine-backup --mode=restore did not filter expected errors, which are in English, and failed. To fix this, engine-backup --mode=restore was changed to require lc_messages to be en_US.UTF-8, and engine-setup was changed to set lc_messages to en_US.UTF-8 on clean installs, and require that on upgrades (and abort otherwise). Now, if lc_messages is not en_US.UTF-8, engine-backup --mode=restore exits with a more helpful error message. engine-setup sets it correctly on clean installs even if the system locale is different, and aborts on upgrades if it is not set correctly.
Story Points:	---
Clone Of:
Clones:	1192954 (view as bug list)
Environment:
Last Closed:	2016-03-09 15:53:18 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	Integration
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Flags:	ylavi: Triaged+

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Knowledge Base (Solution)	2138121	None	None	None	2016-01-25 05:33 EST
oVirt gerrit	37193	master	ABANDONED	packaging: engine-backup: filter errors by codes	Never
oVirt gerrit	37806	master	MERGED	packaging: setup: pg conf check/set lc_messages	Never
oVirt gerrit	37809	master	MERGED	packaging: engine-backup: Require lc_messages = en_US.UTF-8	Never
oVirt gerrit	37811	ovirt-engine-3.5	ABANDONED	packaging: setup: pg conf check/set lc_messages	Never
oVirt gerrit	37812	ovirt-engine-3.5	MERGED	packaging: engine-backup: Require lc_messages = en_US.UTF-8	Never
oVirt gerrit	37814	master	MERGED	packaging: setup: Fix check of pg conf	Never
oVirt gerrit	37815	ovirt-engine-3.5	ABANDONED	packaging: setup: Fix check of pg conf	Never
oVirt gerrit	37828	master	MERGED	packaging: setup: Move provisioning init to common	Never
oVirt gerrit	37870	master	MERGED	packaging: setup: clean up db connection plugins	Never
Red Hat Product Errata	RHEA-2016:0376	normal	SHIPPED_LIVE	Red Hat Enterprise Virtualization Manager 3.6.0	2016-03-09 20:20:52 EST

Groups: None (edit)

Comment 5 Sandro Bonazzola 2015-01-09 09:11:49 EST

Initially targeting to 3.6 while the issue will be investigated.

Comment 6 Yedidyah Bar David 2015-01-21 08:54:56 EST

Seems like the problem is due to a locale in which 'Language "plpgsql" already exists' is translated - still didn't reproduce.

Comment 9 Yedidyah Bar David 2015-01-25 05:53:47 EST

We have some technical difficulties working with lc_messages set to some non-en-US locale. In this bug, about engine-backup, which uses psql to restore, we found some workaround, but we want to apply the same logic in engine-setup (see bug 1078871), which uses pg_restore, where a similar workaround does not seem possible.

How important it is to support foreign locales? Will it be an acceptable solution if our tools (engine-setup, engine-backup) support only en_US.UTF-8, check this early and abort otherwise?

BTW, please verify that this indeed is the problem - if so, the following should be a workaround:

Edit /var/lib/pgsql/data/postgresql.conf
Find lc_messages, it should probably be:
lc_messages = 'ja_JP.UTF-8'
Change this line to be:
lc_messages = 'en_US.UTF-8'
Then restart postgresql (you might need to stop connected clients, including the engine, dwhd).

Comment 15 Jiri Belka 2015-04-16 10:44:34 EDT

ok, ovirt-engine-setup-3.6.0-0.0.master.20150412172306.git55ba764.el6.noarch

works exactly as described in #11

Comment 16 Nicolas Ecarnot 2015-12-30 08:11:33 EST

(In reply to Yedidyah Bar David from comment #9)
> How important it is to support foreign locales?

Though I'm french, I very often prefer getting English reports, messages and log files. Moreover, if it could break anything, please choose English.

> BTW, please verify that this indeed is the problem - if so, the following
> should be a workaround

Working workaround.

Comment 17 Yedidyah Bar David 2015-12-30 08:18:47 EST

(In reply to Nicolas Ecarnot from comment #16)
> (In reply to Yedidyah Bar David from comment #9)
> > How important it is to support foreign locales?
> 
> Though I'm french, I very often prefer getting English reports, messages and
> log files. Moreover, if it could break anything, please choose English.
> 
> > BTW, please verify that this indeed is the problem - if so, the following
> > should be a workaround
> 
> Working workaround.

Thanks for the report!

Comment 20 errata-xmlrpc 2016-03-09 15:53:18 EST

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2016-0376.html

Note You need to log in before you can comment on or make changes to this bug.