Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1093845

Summary:	We should automatically set the correct DB character encoding
Product:	[Community] Spacewalk	Reporter:	Stephen Herr <sherr>
Component:	Server	Assignee:	Stephen Herr <sherr>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	2.2
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	spacewalk-setup-postgresql-2.2.2-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-07-17 08:41:24 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1119298

Description Stephen Herr 2014-05-02 19:47:23 UTC

Description of problem:
UTF-8 is the only valid database character encoding on Spacewalk servers. However currently instead of setting it automatically we take whatever the server-wide character encoding is. This will lead to problems later if it's not set to UTF-8.

This bug will track the change to make the tooling always correctly select UTF-8 as the DB character encoding. However we also need to make sure that if the system encoding is non-UTF-8 that other parts of Spacewalk do not break.

See bug 1085151 for the discussion that lead to this.

Comment 1 Stephen Herr 2014-05-02 19:56:55 UTC

Committed to Spacewalk master:
58871a80270e6b6b04e21a20ec910497674709e7

Comment 2 Milan Zázrivec 2014-07-17 08:41:24 UTC

Spacewalk 2.2 has been released:

    https://fedorahosted.org/spacewalk/wiki/ReleaseNotes22