Comment 35 for bug 1533082

Unfortunately, there is no evidence from mco/puppet side about this problem. If we try to run this task with '-d' flag, it shows that ntpdate successfully ran, send one package, then just hangs:

^_^ -> less node-4.test.domain.local/ntpdate.log
2016-01-25T18:45:57.616378+00:00 notice: transmit(10.109.16.2)
2016-01-25T18:45:57.616450+00:00 notice: receive(10.109.16.2)
node-4.test.domain.local/ntpdate.log (END)

At this exact moment each other node ran ntpdate succesfully:
^_^ -> less node-5.test.domain.local/ntpdate.log
2016-01-25T18:45:55.613334+00:00 notice: transmit(10.109.16.2)
2016-01-25T18:45:55.613894+00:00 notice: receive(10.109.16.2)
2016-01-25T18:45:57.613337+00:00 notice: transmit(10.109.16.2)
2016-01-25T18:45:57.613533+00:00 notice: receive(10.109.16.2)
2016-01-25T18:45:59.613488+00:00 notice: transmit(10.109.16.2)
2016-01-25T18:45:59.613488+00:00 notice: adjust time server 10.109.16.2 offset -0.000337 sec
2016-01-25T18:45:59.613499+00:00 notice: receive(10.109.16.2)
2016-01-25T18:45:59.613601+00:00 notice: server 10.109.16.2, port 123
2016-01-25T18:45:59.613693+00:00 notice: stratum 4, precision -24, leap 00, trust 000
2016-01-25T18:45:59.613790+00:00 notice: refid [10.109.16.2], delay 0.02594, dispersion 0.00012
2016-01-25T18:45:59.613874+00:00 notice: transmitted 4, in filter 4
2016-01-25T18:45:59.613979+00:00 notice: reference time: da50eba7.9627817c Mon, Jan 25 2016 18:44:55.586
2016-01-25T18:45:59.614090+00:00 notice: originate timestamp: da50ebe7.9cea9f10 Mon, Jan 25 2016 18:45:59.612
2016-01-25T18:45:59.614184+00:00 notice: transmit timestamp: da50ebe7.9cfc135d Mon, Jan 25 2016 18:45:59.613
2016-01-25T18:45:59.614268+00:00 notice: filter delay: 0.02594 0.02623 0.02611 0.02597
2016-01-25T18:45:59.614360+00:00 notice: 0.00000 0.00000 0.00000 0.00000
2016-01-25T18:45:59.614467+00:00 notice: filter offset: -0.00033 -0.00048 -0.00050 -0.00049
2016-01-25T18:45:59.614795+00:00 notice: 0.000000 0.000000 0.000000 0.000000
2016-01-25T18:45:59.614795+00:00 notice: delay 0.02594, dispersion 0.00012
2016-01-25T18:45:59.614801+00:00 notice: offset -0.000337
2016-01-25T18:45:59.614872+00:00 notice:
2016-01-25T18:45:59.615103+00:00 notice: 25 Jan 18:45:59 ntpdate[8103]: adjust time server 10.109.16.2 offset -0.000337 sec
2016-01-25T18:45:59.616662+00:00 notice: ntpdate 4.2.6p5@1.2349-o Thu Jan 21 23:29:28 UTC 2016 (1)
2016-01-25T18:46:05.718935+00:00 notice: adjust time server 10.109.16.2 offset -0.000435 sec

I trying to reproduce this task with strace patch, but with no luck yet. As we know that problem is in ntpdate itself and not at library side, I kindly ask mos-linux team take a look into this to shed some light.