Project

General

Profile

action #20310

[qe-core][qem] have a reference system patch and reboot in a specific time

Added by coolo over 5 years ago. Updated 10 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
New test
Target version:
-
Start date:
2017-07-07
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

We have several test that patch_and_reboot, but we have none where we expect
the system in a specific time to be alive again. Meaning LAMP stack back on.

As the recent openssl regression showed, this is crucial not to miss - the default
timeouts are just too forgiving (and do not check if postgresql/mysql/apache/openssh
start in time).

History

#1 Updated by pcervinka over 3 years ago

  • Assignee set to osukup

osukup, is it there anything we can do about it?

#2 Updated by tjyrinki_suse about 2 years ago

  • Subject changed from [qam] have a reference system patch and reboot in a specific time to [qe-core][qam] have a reference system patch and reboot in a specific time

#3 Updated by osukup about 2 years ago

  • Assignee deleted (osukup)

#4 Updated by tjyrinki_suse about 2 years ago

  • Subject changed from [qe-core][qam] have a reference system patch and reboot in a specific time to [qe-core][qem] have a reference system patch and reboot in a specific time

#5 Updated by okurz 10 months ago

This ticket was set to "Normal" priority but was not updated within the SLO period for "Normal" tickets (365 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives. Please consider picking up this ticket within the next 365 days or just set the ticket to the next lower priority of "Low" (no SLO related time period).

Also available in: Atom PDF