rsyslog time is still the default timezone after deployment if it's changed
Bug #1819548 reported by
Alex Schultz
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Medium
|
Alex Schultz |
Bug Description
If a user configures the system local or timezone to something other than the default from the overcloud image, when the system is updated the rsyslog logs are still in the original timezone. After we configure the timezone we need to trigger a rsyslog reload in order to have the changes take effect.
tags: | added: queens-backport-potential |
Changed in tripleo: | |
milestone: | none → stein-3 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/642587
Review: https:/