kolla-ansible

chrony doesn't work when no ntp server

Bug #1705200 reported by Jeffrey Zhang
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla-ansible
Fix Released
Undecided
Jeffrey Zhang
kolla-ansible pike-3 "pike"
Ocata
Fix Released
Undecided
Unassigned

Bug Description

chrony doesn't work when there is no extra ntp server or internet.

in the old implementation, chrony-server only support one server. if you config multi chrony-server, since there is not sync mech in ntp, the client will failed to sync with these servers.

So the better to implement multi ntp server is sync through vip address.

Jeffrey Zhang (jeffrey4l)
Changed in kolla-ansible:
milestone: none → pike-3
Jeffrey Zhang (jeffrey4l)
Changed in kolla-ansible:
assignee: nobody → Jeffrey Zhang (jeffrey4l)
OpenStack Infra (hudson-openstack)
Changed in kolla-ansible:
status: New → In Progress
Revision history for this message
Jeffrey Zhang (jeffrey4l) wrote :

here is the master branch patch https://review.openstack.org/485083

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla-ansible (master)

Reviewed: https://review.openstack.org/485083
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=72ee7dac7c2471efec145d04158e801379b5fa3a
Submitter: Jenkins
Branch: master

commit 72ee7dac7c2471efec145d04158e801379b5fa3a
Author: Jeffrey Zhang <email address hidden>
Date: Sun Jun 18 20:59:28 2017 +0800

    Support multi local chrony servers

    In the old implementation, if there is no external ntp server, only one
    local chrony server is supported. If multi chrony-server is configured,
    chrony client can not sync with them.

    In the new implementation
    * use VIP to connect chrony-server, which ensure multi local chrony
      servers are supported.
    * chrony servers depend on VIP. So chrony-server group should be
      the same with haproxy group.
    * prevent chrony client sync from itself.
    * Change owner to chrony:kolla for chrony log folder
    * fix keysfile path
    * use chrony user for centos and ubuntu image
    * fix permission issue for /var/lib/chrony folder

    Closes-Bug: #1705200
    Change-Id: I6e85fda9824b5ddc7a96895425c5932a3566c27e

Changed in kolla-ansible:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kolla-ansible 5.0.0.0b3

This issue was fixed in the openstack/kolla-ansible 5.0.0.0b3 development milestone.

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

Reviewed: https://review.openstack.org/487754
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=9c0963a5f789748ff6cf858c6444d832bc8f497c
Submitter: Jenkins
Branch: stable/ocata

commit 9c0963a5f789748ff6cf858c6444d832bc8f497c
Author: Jeffrey Zhang <email address hidden>
Date: Sun Jun 18 20:59:28 2017 +0800

    Support multi local chrony servers

    In the old implementation, if there is no external ntp server, only one
    local chrony server is supported. If multi chrony-server is configured,
    chrony client can not sync with them.

    In the new implementation
    * use VIP to connect chrony-server, which ensure multi local chrony
      servers are supported.
    * chrony servers depend on VIP. So chrony-server group should be
      the same with haproxy group.
    * prevent chrony client sync from itself.
    * Change owner to chrony:kolla for chrony log folder
    * fix keysfile path
    * use chrony user for centos and ubuntu image
    * fix permission issue for /var/lib/chrony folder

    Closes-Bug: #1705200
    Change-Id: I6e85fda9824b5ddc7a96895425c5932a3566c27e
    (cherry picked from commit 72ee7dac7c2471efec145d04158e801379b5fa3a)

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kolla-ansible 4.0.3

This issue was fixed in the openstack/kolla-ansible 4.0.3 release.

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

Other bug subscribers

Remote bug watches

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