Project

General

Profile

Actions

action #38093

closed

[sle][functional] Rename the module force_cron_run, it is no more only for cron jobs

Added by SLindoMansilla about 6 years ago. Updated about 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Enhancement to existing tests
Target version:
-
Start date:
2018-07-02
Due date:
% Done:

0%

Estimated time:
Difficulty:
easy

Description

The test module force_cron_run was created in order to execute cron jobs on a controlled environment so that planned tasks on the SUT could not affect the performance of other modules, when those tasks were executed in parallel.

Since Leap/SLE 15, a next step "migrating" into systemd causes that some of those planned maintenance tasks are executed as systemd timers and then we are seeing again those performance issues that were handled by force_cron_run.

The test module was adapted to the systemd changes and now it also handles systemd timers. So the name of the module force_cron_run has to be changed to something that includes both cases.

Acceptance criteria

  • AC1: The test module force_cron_run is renamed to force_maintenance_tasks_run.
  • AC2: The schedule of the renamed module is not altered.

Further information

Some affected scenarios (latest jobs):


Related issues 1 (0 open1 closed)

Related to openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)Resolvedzluo2018-02-032018-07-03

Actions
Actions #1

Updated by SLindoMansilla about 6 years ago

  • Related to action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally) added
Actions #2

Updated by okurz about 6 years ago

  • Status changed from New to In Progress
  • Assignee set to okurz
Actions #4

Updated by okurz about 6 years ago

  • Status changed from In Progress to Resolved
Actions

Also available in: Atom PDF