Project

General

Profile

Actions

action #87982

open

[qe-core] Salt openQA tests are not running on SLE Staging

Added by PSuarezHernandez over 3 years ago. Updated about 1 month ago.

Status:
Workable
Priority:
Normal
Assignee:
Category:
New test
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

We have the following openQA test for doing some smoke test for Salt: https://openqa.opensuse.org/tests/1593451/modules/salt/steps/1/src

while this test is running on "Factory Staging" it does not on "SLE Staging".

We found already situations in the past where we got this test failing in "Factory Staging" because "salt-minion" was not able to run in such minimal environment.
Maybe it's worth to enable this test also in "SLE Staging".

The test would require "Server Application Module", so apparentely it would probably fit into "minimal+base".

I've been discussing this issue already with fcrozat
Thanks in advance!


Factory Staging (in O3) and SLE Staging (in OSD - https://openqa.suse.de/group_overview/125) are job groups that release managers use as a health check. If those are passing, managers know the applied updates are smoke tested ok.

Acceptance Criteria

AC0: Ask for clarification from PSuarezHernandez what tests exactly are to be added. Ask from release managers if this change is ok. Santiago to write names here :)
AC1: Schedule the existing tests - a list gotten from Pablo - to SLE Staging that is already running in Factory.
AC2: Acceptance Criteria are updated and Task is set to workable again for the team to pick it up next sprint

Actions #1

Updated by okurz over 3 years ago

  • Project changed from QA to openQA Tests
  • Category set to New test
Actions #2

Updated by szarate about 3 years ago

  • Subject changed from Salt openQA tests are not running on SLE Staging to [qe-core] Salt openQA tests are not running on SLE Staging
Actions #3

Updated by tjyrinki_suse almost 3 years ago

  • Status changed from New to Workable
  • Start date deleted (2021-01-19)
Actions #4

Updated by szarate almost 3 years ago

  • Priority changed from Normal to High
Actions #5

Updated by okurz over 2 years ago

This ticket was set to "High" priority but was not updated within the SLO period for "High" tickets (30 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 30 days or just set the ticket to the next lower priority of "Normal" (SLO: updated within 365 days). This update was done as agreed within the SUSE QE Sync call 2021-09-01

Actions #6

Updated by okurz over 2 years ago

  • Priority changed from High to Normal

This ticket was set to "High" priority but was not updated within the SLO period for "High" tickets (30 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives . The ticket will be set to the next lower priority of "Normal".

Actions #7

Updated by apappas over 2 years ago

  • Target version set to QE-Core: Ready
Actions #8

Updated by tjyrinki_suse about 2 years ago

  • Description updated (diff)
Actions #9

Updated by szarate about 2 years ago

  • Status changed from Workable to New

This isn't really workable if there are still questions and information to be found out.

Actions #10

Updated by szarate about 2 years ago

  • Tags set to qe-core-april-sprint
  • Description updated (diff)
  • Status changed from New to Workable
  • Assignee set to szarate
Actions #11

Updated by szarate about 2 years ago

Is the status of this ticket current? any updates? can we resolve the ticket?

Actions #12

Updated by szarate about 2 years ago

  • Sprint set to QE-Core: April Sprint (Apr 13 - May 11)
Actions #13

Updated by szarate almost 2 years ago

  • Sprint deleted (QE-Core: April Sprint (Apr 13 - May 11))
Actions #14

Updated by slo-gin about 1 month ago

This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Actions

Also available in: Atom PDF