Project

General

Profile

Actions

action #95872

closed

[sporadic]test fails in ntp_client - time could not be synced

Added by okurz almost 3 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
2021-07-22
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario sle-15-SP3-JeOS-for-kvm-and-xen-Updates-x86_64-jeos-extratest@64bit-virtio-vga fails in
ntp_client
due to which looks like that the time could not be properly synced. The test calls chronyc waitsync 40 0.01 but then fails with the output (see below)

Reproducible

Fails since longer sporadically

Expected result

For reference, good case: 20210721-1 (or more recent)

Suggestions

  • Please add useful description to the test suite including maintainer, e.g. qe-core@suse.de mailing list
  • If you are convinced this is a product bug then try to reproduce the issue better. In the current form bug assignees will not be able to fix any issue. (possibly a product bug?)
  • Try to figure out better what the test is actually doing, ping Dominik if needed
  • Investigate why we're not running it elsewhere (and/or if we have a similar test in a different module)

Further details

Always latest result in this scenario: latest

# wait_serial expected: qr/C3rGQ-\d+-/
# Result:

try: 1, refid: 00000000, correction: 0.000000000, skew: 0.000
try: 2, refid: 00000000, correction: 0.000000000, skew: 0.000
try: 3, refid: 00000000, correction: 0.000000000, skew: 0.000
try: 4, refid: 00000000, correction: 0.000000000, skew: 0.000
try: 5, refid: 00000000, correction: 0.000000000, skew: 0.000
try: 6, refid: 00000000, correction: 0.000000000, skew: 0.000
try: 7, refid: 00000000, correction: 0.000000001, skew: 0.000
try: 8, refid: 00000000, correction: 0.000000001, skew: 0.000
try: 9, refid: 00000000, correction: 0.000000001, skew: 0.000
try: 10, refid: 00000000, correction: 0.000000001, skew: 0.000
try: 11, refid: 00000000, correction: 0.000000001, skew: 0.000
try: 12, refid: 00000000, correction: 0.000000001, skew: 0.000
try: 13, refid: 00000000, correction: 0.000000001, skew: 0.000
try: 14, refid: 00000000, correction: 0.000000001, skew: 0.000
try: 15, refid: 00000000, correction: 0.000000001, skew: 0.000
try: 16, refid: 00000000, correction: 0.000000001, skew: 0.000
try: 17, refid: 00000000, correction: 0.000000001, skew: 0.000
try: 18, refid: 00000000, correction: 0.000000002, skew: 0.000
try: 19, refid: 00000000, correction: 0.000000002, skew: 0.000
try: 20, refid: 00000000, correction: 0.000000002, skew: 0.000
try: 21, refid: 2E0468EA, correction: 40.215045929, skew: 33.852
try: 22, refid: 2E0468EA, correction: 39.444789886, skew: 33.852
try: 23, refid: 2E0468EA, correction: 38.674365997, skew: 33.852
try: 24, refid: 2E0468EA, correction: 37.904544830, skew: 33.852
try: 25, refid: 2E0468EA, correction: 37.134384155, skew: 33.852
try: 26, refid: 2E0468EA, correction: 36.364212036, skew: 33.852
try: 27, refid: 2E0468EA, correction: 35.594066620, skew: 6.661
try: 28, refid: 2E0468EA, correction: 34.823974609, skew: 6.661
try: 29, refid: 2E0468EA, correction: 34.052383423, skew: 6.661
try: 30, refid: 2E0468EA, correction: 33.282390594, skew: 6.661
try: 31, refid: 2E0468EA, correction: 32.512279510, skew: 6.661
try: 32, refid: 2E0468EA, correction: 31.742113113, skew: 6.661
try: 33, refid: 2E0468EA, correction: 30.971427917, skew: 6.661
try: 34, refid: A5E4180F, correction: 30.203792572, skew: 8.379
try: 35, refid: A5E4180F, correction: 29.432651520, skew: 8.379
try: 36, refid: A5E4180F, correction: 28.662019730, skew: 8.379
try: 37, refid: A5E4180F, correction: 27.890933990, skew: 8.379
try: 38, refid: A5E4180F, correction: 27.120006561, skew: 8.379
try: 39, refid: A5E4180F, correction: 26.349527359, skew: 8.379
try: 40, refid: A5E4180F, correction: 25.579122543, skew: 5.645
C3rGQ-1-

in other cases like https://openqa.suse.de/tests/6370944#step/ntp_client/51 there is

# wait_serial expected: qr/C3rGQ-\d+-/
# Result:

try: 1, refid: 00000000, correction: 0.000000000, skew: 0.000
try: 2, refid: 00000000, correction: 0.000000000, skew: 0.000
try: 3, refid: 00000000, correction: 0.000000000, skew: 0.000
…
try: 38, refid: 00000000, correction: 0.000000003, skew: 0.000
try: 39, refid: 00000000, correction: 0.000000004, skew: 0.000
try: 40, refid: 00000000, correction: 0.000000004, skew: 0.000
C3rGQ-1-

similar in https://openqa.suse.de/tests/6349911#step/ntp_client/51 as well as https://openqa.suse.de/tests/6345577#step/ntp_client/51


Related issues 1 (0 open1 closed)

Related to openQA Tests - action #72244: [functional][u] test fails in ntp_clientResolveddheidler2020-10-05

Actions
Actions #1

Updated by szarate almost 3 years ago

  • Related to action #72244: [functional][u] test fails in ntp_client added
Actions #2

Updated by szarate almost 3 years ago

  • Description updated (diff)
  • Priority changed from High to Normal
  • Target version set to QE-Core: Ready
Actions #3

Updated by szarate almost 3 years ago

  • Description updated (diff)
Actions #4

Updated by szarate almost 3 years ago

This is mainly running on JeOS, in jeos-extratest, on several machines but same test.

some relevant jobs are
https://openqa.suse.de/tests/6517585 (15-SP4)
https://openqa.suse.de/tests/6530773 (15-SP3)
https://openqa.suse.de/tests/6530758 (15-SP2)

Actions #5

Updated by szarate almost 3 years ago

  • Status changed from New to Workable
Actions #6

Updated by szarate almost 3 years ago

We also have yast2_ntpclient running somewhere, let's maybe fix it for now and pass over the ownership.

Actions #7

Updated by punkioudi over 2 years ago

  • Assignee set to punkioudi
Actions #8

Updated by jlausuch over 2 years ago

Hi guys, any update on this or any ideas how to fix this?
The previous links don't work, so let me provide new links:

Actions #9

Updated by punkioudi about 2 years ago

  • Assignee deleted (punkioudi)
Actions #10

Updated by tjyrinki_suse about 2 years ago

  • Target version deleted (QE-Core: Ready)
  • Parent task set to #102215
Actions #11

Updated by jlausuch about 2 years ago

  • Tags set to bug
  • Project changed from openQA Tests to 208
  • Subject changed from [sporadic][qe-core] test fails in ntp_client - time could not be synced to [sporadic]test fails in ntp_client - time could not be synced
  • Category deleted (Bugs in existing tests)
  • Parent task deleted (#102215)

Moving this to JeOS.

Actions #12

Updated by mloviska about 2 years ago

  • Tags deleted (bug)
  • Project changed from 208 to openQA Tests
  • Status changed from Workable to In Progress
  • Assignee set to mloviska
Actions #13

Updated by mloviska about 2 years ago

I have run ~90 jobs sle-15-SP4-JeOS-for-kvm-and-xen-x86_64-Build150400.5.20-jeos-extratest@uefi-virtio-vga locally without service restart and it seems to fine and stable.
With respect to sle installations do not enable chrony service by default, we cannot really drop this code. Other installations (leap,tw) or deliverables enable chrony.service by default.

Actions #14

Updated by jlausuch about 2 years ago

90 times and all green seems a high ratio to consider the issue irrelevant :)

Actions #15

Updated by mloviska about 2 years ago

  • Status changed from In Progress to Feedback
Actions #16

Updated by mloviska about 2 years ago

  • Status changed from Feedback to Resolved
Actions #18

Updated by openqa_review about 2 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: jeos-extratest
https://openqa.suse.de/tests/8126714

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.

Actions

Also available in: Atom PDF