Project

General

Profile

Actions

action #46379

closed

[sle][migration][sle15sp1]test fails in force_scheduled_tasks - Triggering systemd timed service timeout

Added by tinawang123 over 5 years ago. Updated about 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
-
Start date:
2019-01-18
Due date:
% Done:

100%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario sle-15-SP1-Installer-DVD-aarch64-offline_sles12sp4_media_tcm_all_full@aarch64 fails in
force_scheduled_tasks

Reproducible

Fails since (at least) Build 118.1

Expected result

Last good: (unknown) (or more recent)

Further details

Always latest result in this scenario: latest


Related issues 1 (0 open1 closed)

Related to openQA Tests - action #46835: [functional][u] test fails in force_scheduled_tasks: timeoutResolvedokurz2019-01-292019-02-18

Actions
Actions #1

Updated by leli over 5 years ago

  • Assignee set to leli

We need to check the service state manually, then decide whether this is product bug or not.

Actions #2

Updated by okurz over 5 years ago

I don't think this is any other bug than bsc#1063638, i.e. the bug this whole module was created for. It just seems that just triggering the services can already load the system enough so that the commands do not return within 90 seconds. I suggest to just increase the timeout in this call accordingly.

Actions #3

Updated by leli over 5 years ago

@Oliver, Ok, I will try to increase the timeout value.

Actions #4

Updated by leli about 5 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 50
Actions #5

Updated by okurz about 5 years ago

  • Related to action #46835: [functional][u] test fails in force_scheduled_tasks: timeout added
Actions #6

Updated by okurz about 5 years ago

The timeout of 150s seems to be not enough, continuing in #46835

Actions #7

Updated by okurz about 5 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: offline_sles12sp3_scc_base_all_full_lock
https://openqa.suse.de/tests/2447743

Actions #8

Updated by leli about 5 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 50 to 100

Verified on build 178.3, no such issue found.

Actions

Also available in: Atom PDF