Bug 1688349

Summary: [OSP14] Add a note to reboot the system if the system locale is not en_US.utf-8 or timezone is not America/NewYork.
Product: Red Hat OpenStack Reporter: Alex Schultz <aschultz>
Component: openstack-tripleo-heat-templatesAssignee: Alex Schultz <aschultz>
Status: CLOSED ERRATA QA Contact: Sasha Smolyak <ssmolyak>
Severity: high Docs Contact:
Priority: high    
Version: 14.0 (Rocky)CC: aschultz, dbecker, dcadzow, emacchi, jjoyce, jschluet, knoha, mburns, morazi, nlevinki, rheslop, rhos-docs, rhos-maint, slinaber, tvignaud
Target Milestone: ---Keywords: Triaged, ZStream
Target Release: 14.0 (Rocky)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-heat-templates-9.2.1-0.20190119154872.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1651900 Environment:
Last Closed: 2019-04-30 17:51:15 UTC Type: ---
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: 1651900    

Description Alex Schultz 2019-03-13 15:19:32 UTC 
+++ This bug was initially created as a clone of Bug #1651900 +++

Description of problem:
Add a note to reboot the system if the system locale is not in en_US.utf-8 or timezone is not America/NewYork.

https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html/director_installation_and_usage/chap-configuring_basic_overcloud_requirements_with_the_cli_tools#sect-Completing_the_Overcloud_Creation

Between 6.15 and 6.16, we should have a note and describe the reason.
During overcloud deployment, reboot is not happened after timzone configuration.
Because of that, rsyslog writes its logs with the default timzone, America/NewYork.

It will make troubleshooting complicated.
We should add a note to encourage our user to reboot all overcloud nodes after the deployment.
Comment 10 errata-xmlrpc 2019-04-30 17:51:15 UTC 
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://access.redhat.com/errata/RHBA-2019:0878