|Summary:||Master pods are not matched the timezone with worker nodes and its running host|
|Product:||OpenShift Container Platform||Reporter:||Daein Park <dapark>|
|Component:||Installer||Assignee:||Scott Dodson <sdodson>|
|Installer sub component:||openshift-ansible||QA Contact:||Gaoyun Pei <gpei>|
|Status:||CLOSED ERRATA||Docs Contact:|
|Priority:||unspecified||CC:||dapark, dcaldwel, dlbewley, gpei|
|Fixed In Version:||Doc Type:||Bug Fix|
Previously, timezone configuration was not mounted into the control plane static pods which led to logging timestamps not aligning with all other system logs. The host's timezone configuration is now mounted into the control plane pods.
|Last Closed:||2019-04-11 05:38:26 UTC||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
|Bug Depends On:|
Description Daein Park 2019-02-09 14:57:43 UTC
Comment 1 Scott Dodson 2019-02-11 19:05:14 UTC
Can you try bind mounting /etc/localtime and /usr/share/zoneinfo into the static pod to see if this resolves the problem?
Comment 2 Daein Park 2019-02-11 23:45:51 UTC
Thank you for your workaround @Scott, And the solution you provided is valid to resolve this issue. I've already opened the PR here after verifying same solution: https://github.com/openshift/openshift-ansible/pull/11160 I just mounted only a "/etc/localtime" to resolve it. Do you think it had better to mount additional "/usr/share/zoneinfo" either ?
Comment 3 Scott Dodson 2019-02-12 15:38:01 UTC
I guess that means timezone data is installed inside the container image so it should be safe with only /etc/localtime as long as the base image for the control plane never changes which I can't see happening. I'd like to get some feedback from the pod teams on the change before we move forward.
Comment 4 Scott Dodson 2019-02-28 20:02:10 UTC
Comment 6 Gaoyun Pei 2019-03-18 09:29:37 UTC
Verify this bug with openshift-ansible-3.11.96-1.git.0.c2a3f89.el7.noarch.rpm [root@ip-172-18-8-68 ~]# for pod in $(echo master-api-ip-172-18-8-68.ec2.internal master-controllers-ip-172-18-8-68.ec2.internal master-etcd-ip-172-18-8-68.ec2.internal ); do echo $pod; oc rsh $pod date; done master-api-ip-172-18-8-68.ec2.internal Mon Mar 18 00:45:10 EDT 2019 master-controllers-ip-172-18-8-68.ec2.internal Mon Mar 18 00:45:11 EDT 2019 master-etcd-ip-172-18-8-68.ec2.internal Mon Mar 18 00:45:11 EDT 2019 [root@ip-172-18-8-68 ~]# date Mon Mar 18 00:45:13 EDT 2019 Master pods: api, controller, etcd have the same timezone with the host.
Comment 8 errata-xmlrpc 2019-04-11 05:38:26 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:0636