sync the timezone between the host and the containers

Bug #1577148 reported by Jeffrey Zhang
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla
Fix Released
Undecided
Jeffrey Zhang
Liberty
Won't Fix
Undecided
Jeffrey Zhang
Mitaka
Fix Released
Undecided
Jeffrey Zhang

Bug Description

Normally, the container is using UTC timezone. When the host timezone is changed, the
hardware clock will be changed two. But the container know nothing about the change.
the the time in the container will offset a few hours, which will result in error in the
distribute service. like mariadb galera and ceph.

summary: - Normally, the container is using UTC timezone. When the host timezone is
- changed, the hardware clock will be changed two. But the container know
- nothing about the change. the the time in the container will offset a
- few hours, which will result in error in the distribute service. like
- mariadb galera and ceph.Normally, the container is using UTC timezone.
- When the host timezone is changed, the hardware clock will be changed
- two. But the container know nothing about the change. the the time in
- the container will offset a few hours, which will result in error in the
- distribute service. like mariadb galera and ceph.Normally, the container
- is using UTC timezone. When the host timezone is changed, the hardware
- clock will be changed two. But the container know nothing about the
- change. the the time in the container will offset a few hours, which
- will result in error in the distribute service. like mariadb galera and
- ceph.Normally, the container is using UTC timezone. When the host
- timezone is changed, the hardware clock will be changed two. But the
- container know nothing about the change. the the time in the container
- will offset a few hours, which will result in error in the distribute
- service. like mariadb galera and ceph.Normally, the container is using
- UTC timezone. When the host timezone is changed, the hardware clock
- will be changed two. But the container know nothing about the change.
- the the time in the container will offset a few hours, which will result
- in error in the distribute service. like mariadb galera and
- ceph.Normally, the container is using UTC timezone. When the host
- timezone is changed, the hardware clock will be changed two. But the
- container know nothing about the change. the the time in the container
- will offset a few hours, which will result in error in the distribute
- service. like mariadb galera and ceph.
+ sync the timezone between the host and the containers
Changed in kolla:
assignee: nobody → Jeffrey Zhang (jeffrey4l)
Changed in kolla:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla (master)

Reviewed: https://review.openstack.org/311615
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=0fcee87549dc417c152b16e14c31dea6ada84eb7
Submitter: Jenkins
Branch: master

commit 0fcee87549dc417c152b16e14c31dea6ada84eb7
Author: Jeffrey Zhang <jeffrey.zhang@99cloud.net>
Date: Sun May 1 20:11:45 2016 +0800

    map the host localtime to the container

    Closes-Bug: #1577148
    Change-Id: I636cefc63cf532434a41af3898b63dffa711e280

Changed in kolla:
status: In Progress → Fix Released
Changed in kolla:
milestone: none → newton-1
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to kolla (stable/mitaka)

Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/319021

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla (stable/mitaka)

Reviewed: https://review.openstack.org/319021
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=1a6a3d19f73ad655c6321b66a6da4da27b8b46a1
Submitter: Jenkins
Branch: stable/mitaka

commit 1a6a3d19f73ad655c6321b66a6da4da27b8b46a1
Author: Jeffrey Zhang <jeffrey.zhang@99cloud.net>
Date: Sun May 1 20:11:45 2016 +0800

    map the host localtime to the container

    Closes-Bug: #1577148
    Change-Id: I636cefc63cf532434a41af3898b63dffa711e280
    (cherry picked from commit 0fcee87549dc417c152b16e14c31dea6ada84eb7)

Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/kolla 3.0.0.0b1

This issue was fixed in the openstack/kolla 3.0.0.0b1 development milestone.

Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/kolla 2.0.1

This issue was fixed in the openstack/kolla 2.0.1 release.

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.