docker-puppet.py time handling is hard to debug

Bug #1737954 reported by Jiří Stránský
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
Low
Jiří Stránský

Bug Description

We seem to be sometimes hitting an issue where puppet containers seem to think that /etc/hosts was modified and they try to copy it among the puppet-generated files. This has been originally reported as bug 1709689. It may be easier to debug if we know what mtime was on the_origin_of_time file, and if we mounted /etc/localtime into the container to sync the timezone info between host and container.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-heat-templates (master)

Fix proposed to branch: master
Review: https://review.openstack.org/527673

Changed in tripleo:
assignee: nobody → Jiří Stránský (jistr)
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-heat-templates (master)

Reviewed: https://review.openstack.org/527673
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=51a3b05f4ec952d99935fdbbc64347c0404fd29b
Submitter: Zuul
Branch: master

commit 51a3b05f4ec952d99935fdbbc64347c0404fd29b
Author: Jiri Stransky <email address hidden>
Date: Wed Dec 13 12:33:37 2017 +0100

    Improve debugging possibilities for docker-puppet.py time handling

    We faced issue where on some environments docker-puppet.py picks up
    /etc/hosts as modified, even though that shouldn't be the case (LP bug
    1709689). On the last occasion we found the cause to be desynced time
    on the host machine of a virtual setup, and subsequent NTP sync of
    overcloud nodes (causing a 5 hour skip back in time) racing with
    docker-puppet.py.

    Still, more info to debug these kinds of issues would be nice to
    have. Printing the timestamp of origin_of_time, saving it to a
    persistent directory and making sure /etc/localtime is mounted into
    docker-puppet containers should make finding the root cause on such
    occasions easier.

    Change-Id: I2ea197673b470379ead295058b6952cce3a69606
    Closes-Bug: #1737954

Changed in tripleo:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-heat-templates 8.0.0.0b3

This issue was fixed in the openstack/tripleo-heat-templates 8.0.0.0b3 development milestone.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-heat-templates (stable/pike)

Fix proposed to branch: stable/pike
Review: https://review.openstack.org/543510

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-heat-templates (stable/pike)

Reviewed: https://review.openstack.org/543510
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=9d44e267b8341b40040835b5e4b987930499bc72
Submitter: Zuul
Branch: stable/pike

commit 9d44e267b8341b40040835b5e4b987930499bc72
Author: Jiri Stransky <email address hidden>
Date: Wed Dec 13 12:33:37 2017 +0100

    Improve debugging possibilities for docker-puppet.py time handling

    We faced issue where on some environments docker-puppet.py picks up
    /etc/hosts as modified, even though that shouldn't be the case (LP bug
    1709689). On the last occasion we found the cause to be desynced time
    on the host machine of a virtual setup, and subsequent NTP sync of
    overcloud nodes (causing a 5 hour skip back in time) racing with
    docker-puppet.py.

    Still, more info to debug these kinds of issues would be nice to
    have. Printing the timestamp of origin_of_time, saving it to a
    persistent directory and making sure /etc/localtime is mounted into
    docker-puppet containers should make finding the root cause on such
    occasions easier.

    Change-Id: I2ea197673b470379ead295058b6952cce3a69606
    Closes-Bug: #1737954
    (cherry picked from commit 51a3b05f4ec952d99935fdbbc64347c0404fd29b)

tags: added: in-stable-pike
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-heat-templates 7.0.10

This issue was fixed in the openstack/tripleo-heat-templates 7.0.10 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.