Bug 1312947

Summary:	[RFE] make container time zone match the one of the node
Product:	OpenShift Container Platform	Reporter:	Evgheni Dereveanchin <ederevea>
Component:	RFE	Assignee:	Derek Carr <decarr>
Status:	CLOSED DEFERRED	QA Contact:	Johnny Liu <jialiu>
Severity:	medium	Docs Contact:
Priority:	high
Version:	3.1.0	CC:	amurdaca, aos-bugs, byount, cpitman, dwalsh, ederevea, erich, fcami, fkluknav, hgomes, jhonce, jkaur, jokerman, jrosenta, jseunghw, knakayam, ludovic.piffaretti, mark.vinkx, mbarrett, mburgerh, misalunk, mmccomas, mwysocki, myllynen, stwalter
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-03-12 13:54:36 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Evgheni Dereveanchin 2016-02-29 15:25:36 UTC

Description of request:

Currently containers may have random time zones based on the imaged used. This request is to allow setting a timezone for all containers for ease of auditing and maintenance of containers. An option would be to mount /etc/localtime into all containers so that their time zones match the node's time zone

Version-Release number of selected component (if applicable):
3.1.1

Comment 3 Daniel Walsh 2016-07-02 13:39:16 UTC

The problem with always setting the /etc/localtime into the container, is that it assumes that this means something to the content inside of the container.  For this reason docker upstream has been reluctant to accept patches making this so.  

You can simply volume mount in /etc/localtime and hope for the best.

-v /etc/localtime:/etc/localtime

I suppose we could do this at the higher level tools.  Or at least add a config option to do this.

Comment 4 Chris Pitman 2016-07-13 01:09:03 UTC

Asking users to mount in /etc/timezone also means that all users and containers have to be able to do host mounts, which we are generally restricting in OSCP deployments.

Comment 5 Daniel Walsh 2016-07-13 10:21:14 UTC

Can't we make OSCP do this automatically then?

Comment 32 Eric Rich 2018-03-12 13:54:36 UTC

This bug has been identified as a dated (created more than 3 months ago) bug. 
This bug has been triaged (has a trello card linked to it), or reviewed by Engineering/PM and has been put into the product backlog, 
however this bug has not been slated for a currently planned release (3.9, 3.10 or 3.11), which cover our releases for the rest of the calendar year. 

As a result of this bugs age, state on the current roadmap and PM Score (being below 70), this bug is being Closed - Differed, 
as it is currently not part of the products immediate priorities.

Please see: https://docs.google.com/document/d/1zdqF4rB3ea8GmVIZ7qWCVYUaQ7-EexUrQEF0MTwdDkw/edit for more details.

Comment 33 Frantisek Kluknavsky 2018-04-17 14:48:19 UTC

Some useful hints are also in bug 1399749.