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.
Hi Documentation team, Do you have any updates on this bugzilla? Regards, Keigo Noha
Verified on compose 2019-04-10.1 that rsyslog got restarted after Timezone change apply: ... pr 15 04:41:58 controller-0 os-collect-config: TASK [Check if rsyslog exists] ************************************************* Apr 15 04:41:58 controller-0 os-collect-config: TASK [restart rsyslog service after logging conf change] *********************** Apr 15 04:43:19 controller-0 puppet-user[23464]: (/Stage[main]/Timezone/File[/etc/localtime]/target) target changed '../usr/share/zoneinfo/America/New_York' to '/usr/share/zoneinfo//Asia/Tokyo' Apr 15 17:43:19 controller-0 rsyslogd: [origin software="rsyslogd" swVersion="8.24.0-34.el7" x-pid="18831" x-info="http://www.rsyslog.com"] exiting on signal 15. Apr 15 17:43:19 controller-0 rsyslogd: [origin software="rsyslogd" swVersion="8.24.0-34.el7" x-pid="24109" x-info="http://www.rsyslog.com"] start
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:0939