Comment 34 for bug 1572521
Revision history for this message
| Oleksiy Molchanov (omolchanov) wrote Re: Time on nodes was not set with 'ntpdate' | #34 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
demo site
(Get the code!)
I had a talk with Dmitry Ilyin and made testings. So we have 2 approaches for fixing this bug:
1) Non-controller nodes should sync time with the same ntp-server as controllers
2) You should wait before pacemaker resource p_ntp is up and after that sync time
Personally I prefere 1-st.
Why can't it be fixed in library? In your case pacemaker needs a lot of time to bring up all resources in cluster and ntp resource is the last one in this list. We cannot move it to the top of the list because it has lots of dependencies, like p_vrouter, vip_mgmt and deployment by itself (this resource is created in the post-deployment, that is why it is in the bottom). Even if we could make it start first, you must have some kind of test to check whether it is up, synced and can provide time.