Bug 1310094 - [CentOS7] packstack execution fails immediately on freshly installed system. Complains about inexistent locale.
[CentOS7] packstack execution fails immediately on freshly installed system. ...
Status: CLOSED EOL
Product: RDO
Classification: Community
Component: openstack-packstack (Show other bugs)
Liberty
x86_64 Linux
unspecified Severity medium
: ---
: Kilo
Assigned To: Martin Magr
Shai Revivo
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-02-19 07:36 EST by capriotti.carlos
Modified: 2016-05-19 12:03 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-05-19 12:03:12 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description capriotti.carlos 2016-02-19 07:36:31 EST
Description of problem:

Launching a fresh installation of packstack on a brand new install of CentOS7 (1511) fails due to undefined locale on server. 

Version-Release number of selected component (if applicable):

CentOS7 (1511) + OpenStack Liberty

How reproducible:

Fresh install of CentOS7 (Infrastructure server + NFS client), and follow instructions from

https://www.rdoproject.org/install/quickstart/

Steps to Reproduce:
1. Install CentOS7
2. Follow instructions from https://www.rdoproject.org/install/quickstart/


Additional info:

As a workaround, populate 

/etc/environment


with 


LANG=en_US.utf-8
LC_ALL=en_US.utf-8


Note: may not be directly related to RDO, but here are two suggestions: 

a) add this info/workaround to the instructions page, just in case. 
b) installation script should check for it and issue a human-readable, easy to interpret error message.
Comment 2 Chandan Kumar 2016-05-19 12:03:12 EDT
This bug is against a Version which has reached End of Life.
If it's still present in supported release (http://releases.openstack.org), please update Version and reopen.

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