time and timezone on container not the same as that on host

Bug #1707700 reported by Vedamurthy Joshi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
R4.0
Fix Committed
High
Siva Gurumurthy
Trunk
Fix Committed
High
Siva Gurumurthy

Bug Description

R4.0.1.0 27, Ubuntu 14.04

It is seen on multiple testbeds that the timestamp in the container is different from that on host.
Also, even though /etc/timezone is set as expected, date continues to show UTC

root@nodem14:~# date
Mon Jul 31 23:48:39 IST 2017
root@nodem14:~# docker exec -it controller date
Mon Jul 31 18:18:45 UTC 2017
root@nodem14:~# docker exec -it controller cat /etc/timezone
Asia/Kolkata
root@nodem14:~# cat /etc/timezone
Asia/Kolkata
root@nodem14:~#

Tags: blocker sanity
tags: added: blocker
removed: bloc
Changed in juniperopenstack:
assignee: nobody → Abhay Joshi (abhayj)
Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] master

Review in progress for https://review.opencontrail.org/34188
Submitter: Rasika Uday Dravid (<email address hidden>)

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] R4.0

Review in progress for https://review.opencontrail.org/34189
Submitter: Rasika Uday Dravid (<email address hidden>)

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : A change has been merged

Reviewed: https://review.opencontrail.org/34188
Committed: http://github.com/Juniper/contrail-ansible/commit/52b74a1c6665f206da147f1640ea3854039e5220
Submitter: Zuul (<email address hidden>)
Branch: master

commit 52b74a1c6665f206da147f1640ea3854039e5220
Author: Rasika Dravid <email address hidden>
Date: Mon Jul 31 19:22:35 2017 -0700

time and timezone on container not the same as that on host

Today time and timezone on container is same as host machine.
Earlier timezone was showing a default value Etc/UTC and time
on container and host machine was different. Now this code
shows the time and timezone same as that of host machine.

Change-Id: I0bb492a65b5ca507084808286659ae42e3f582c0
Closes-Bug: #1707700

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote :

Reviewed: https://review.opencontrail.org/34189
Committed: http://github.com/Juniper/contrail-ansible/commit/1ef637733d2c6cf2af5bdcc1032d1df560da4d6f
Submitter: Zuul (<email address hidden>)
Branch: R4.0

commit 1ef637733d2c6cf2af5bdcc1032d1df560da4d6f
Author: Rasika Dravid <email address hidden>
Date: Mon Jul 31 19:22:35 2017 -0700

time and timezone on container not the same as that on host

Today time and timezone on container is same as host machine.
Earlier timezone was showing a default value Etc/UTC and time
on container and host machine was different. Now this code
shows the time and timezone same as that of host machine.

Change-Id: I0bb492a65b5ca507084808286659ae42e3f582c0
Closes-Bug: #1707700

Revision history for this message
Vedamurthy Joshi (vedujoshi) wrote :

I still see the problem in 4.0.1.0 continuous build 19

root@nodek3(agent):/# date
Mon Aug 14 09:36:30 UTC 2017
root@nodek3(agent):/# cat /etc/timezone
Etc/UTC
root@nodek3(agent):/# exit
exit
root@nodek3:/var/log/contrail/cni# date
Mon Aug 14 15:06:40 IST 2017
root@nodek3:/var/log/contrail/cni# cat /etc/timezone
Asia/Kolkata
root@nodek3:/var/log/contrail/cni#

root@nodek3(agent):/# contrail-version
Package Version Build-ID | Repo | Package Name
-------------------------------------- ------------------------------ ----------------------------------
contrail-k8s-cni 4.0.1.0-19 19
contrail-lib 4.0.1.0-19 19
contrail-nodemgr 4.0.1.0-19 19
contrail-setup 4.0.1.0-19 19
contrail-utils 4.0.1.0-19 19
contrail-vrouter-agent 4.0.1.0-19 19
contrail-vrouter-common 4.0.1.0-19 19
contrail-vrouter-dkms 4.0.1.0-19 19
contrail-vrouter-init 4.0.1.0-19 19
contrail-vrouter-utils 4.0.1.0-19 19
python-contrail 4.0.1.0-19 19
python-contrail-vrouter-api 4.0.1.0-19 19
python-opencontrail-vrouter-netns 4.0.1.0-19 19
root@nodek3(agent):/#

Revision history for this message
Siva Gurumurthy (sgurumurthy) wrote :

SM does not support kubernetes.
If you provision using SM it will work

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.