Bug 1093845 - We should automatically set the correct DB character encoding
Summary: We should automatically set the correct DB character encoding
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Spacewalk
Classification: Community
Component: Server
Version: 2.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Stephen Herr
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: space22
TreeView+ depends on / blocked
 
Reported: 2014-05-02 19:47 UTC by Stephen Herr
Modified: 2014-07-17 08:41 UTC (History)
0 users

Fixed In Version: spacewalk-setup-postgresql-2.2.2-1
Clone Of:
Environment:
Last Closed: 2014-07-17 08:41:24 UTC
Embargoed:

Attachments (Terms of Use)

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
Note You need to log in before you can comment on or make changes to this bug.