ntp-dev package affected systest

Bug #1410884 reported by Dmitry Tyzhnenko
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Released
Critical
Dmitry Tyzhnenko
5.1.x
Invalid
Critical
Stanislaw Bogatkin
6.0.x
Invalid
Critical
Fuel QA Team

Bug Description

In review https://review.openstack.org/#/c/135905/ package ntp was replaced to ntp-dev. New package have different init.d scripts in Ubuntu and CentOS. Ubuntu has ntp-dev, CentOS has ntpd. This is affect revert method in systests.

Now systests can't time sync after reverting Ubuntu slave nodes.

Tags: system-tests
Revision history for this message
Dennis Dmitriev (ddmitriev) wrote :

Confirmed on fuel-6.1-60. Regexp in the systests, which should determine the name of the NTP init script, returns nothing, so it just kill ntpd:

root@node-3:~# /etc/init.d/ntp-dev status
 * NTP server is not running

root@node-3:~# find /etc/init.d/ -regex '/etc/init.d/ntp-d.?'
root@node-3:~#

Changed in fuel:
status: New → Confirmed
importance: Undecided → High
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-main (master)

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

Changed in fuel:
assignee: Fuel QA Team (fuel-qa) → Dmitry Tyzhnenko (dtyzhnenko)
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-main (master)

Reviewed: https://review.openstack.org/147572
Committed: https://git.openstack.org/cgit/stackforge/fuel-main/commit/?id=6129a09786c3d422d32f27d176498faaa5a1e898
Submitter: Jenkins
Branch: master

commit 6129a09786c3d422d32f27d176498faaa5a1e898
Author: Dmitry Tyzhnenko <email address hidden>
Date: Thu Jan 15 18:05:24 2015 +0200

    New regex for find different init script for ntpd

    Provide extended regular expression in sync_node_time()
        Works for 'ntpd' and 'ntp-dev' init scripts

    Change-Id: Ie331bfedfa5c1af0132cbb1287a933c14eea253f
    Closes-bug: 1410884

Changed in fuel:
status: In Progress → Fix Committed
Changed in fuel:
status: Fix Committed → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-main (stable/5.1)

Fix proposed to branch: stable/5.1
Review: https://review.openstack.org/150380

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-main (stable/5.1)

Reviewed: https://review.openstack.org/150380
Committed: https://git.openstack.org/cgit/stackforge/fuel-main/commit/?id=95865ec6b38adf80299d98aa5ee9710a337a422e
Submitter: Jenkins
Branch: stable/5.1

commit 95865ec6b38adf80299d98aa5ee9710a337a422e
Author: Dmitry Tyzhnenko <email address hidden>
Date: Thu Jan 15 18:05:24 2015 +0200

    5.1 New regex for find different init script for ntpd

    Provide extended regular expression in sync_node_time()
        Works for 'ntpd' and 'ntp-dev' init scripts

    Change-Id: Ie331bfedfa5c1af0132cbb1287a933c14eea253f
    Closes-bug: 1410884
    (cherry picked from commit 6129a09786c3d422d32f27d176498faaa5a1e898)

Revision history for this message
Stanislaw Bogatkin (sbogatkin) wrote :

Why that bug assigned to 5.1 and 6.0 branches? We only have ntp-dev in 6.1.

Revision history for this message
Timur Nurlygayanov (tnurlygayanov) wrote :

Stanislaw, because our BVT tests for 5.1.x failed with the error:
AssertionError: Failed to execute "NTPD=$(find /etc/init.d/ -regex '/etc/init.d/\(ntp.?\|ntp-dev\)'); $NTPD stop; killall ntpd; ntpd -qg && $NTPD start" on remote host: ['ntpd: no process killed\n']

http://jenkins-product.srt.mirantis.net:8080/view/Staging%20Mirrors/job/5.1.2.staging.centos.bvt_1/28/console

Revision history for this message
Tatyanka (tatyana-leontovich) wrote :

https://review.openstack.org/#/c/150380/ for 5.1 fix was backported

Revision history for this message
ruhe (ruhe) wrote :

Raised to critical because this issue caused failures in staging jobs for 5.1.2

Changed in fuel:
importance: High → Critical
Revision history for this message
Tatyanka (tatyana-leontovich) wrote :

actually we try to kill process that we already stop. So we failed(but actually time synced)

Revision history for this message
Timur Nurlygayanov (tnurlygayanov) wrote :

Looks like the issue in our deployment / test scripts and we need to fix it.

Revision history for this message
Tatyanka (tatyana-leontovich) wrote :

So still are looking on this, manual attempts to sync time failed with "no suitable server to sync" erros.

Revision history for this message
Tatyanka (tatyana-leontovich) wrote :

After triage move issue to invalid for 5.1.x and 6.0.x . Separate issue was created https://bugs.launchpad.net/fuel/+bug/1415596

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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