Project

General

Profile

Actions

action #87982

closed

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

Added by PSuarezHernandez almost 4 years ago. Updated 23 days ago.

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

0%

Estimated time:
Difficulty:
Sprint:
QE-Core: September Sprint 24 (Sep 05 - Oct 03)

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
AC3: Test is enabled in SL Micro 6.0, 6.1 and 5.5

Actions #1

Updated by okurz almost 4 years ago

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

Updated by szarate almost 4 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 over 3 years ago

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

Updated by szarate over 3 years ago

  • Priority changed from Normal to High
Actions #5

Updated by okurz about 3 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 about 3 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 almost 3 years ago

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

Updated by tjyrinki_suse over 2 years ago

  • Description updated (diff)
Actions #9

Updated by szarate over 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 over 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 over 2 years ago

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

Actions #12

Updated by szarate over 2 years ago

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

Updated by szarate over 2 years ago

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

Updated by slo-gin 8 months 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 #15

Updated by szarate 4 months ago

  • Tags changed from qe-core-april-sprint to qe-core-april-sprint, qe-core-august-sprint
Actions #16

Updated by szarate 3 months ago

  • Sprint set to QE-Core: August Sprint 24 (Aug 14 - Aug 28)
Actions #17

Updated by szarate 3 months ago

  • Description updated (diff)
  • Assignee deleted (szarate)
Actions #18

Updated by szarate 3 months ago

  • Sprint changed from QE-Core: August Sprint 24 (Aug 14 - Aug 28) to QE-Core: September Sprint 24 (Sep 05 - Oct 03)
Actions #19

Updated by szarate about 2 months ago

  • Tags changed from qe-core-april-sprint, qe-core-august-sprint to qe-core-april-sprint, qe-core-august-sprint, qe-core-october-sprint
Actions #20

Updated by rfan1 about 1 month ago

  • Status changed from Workable to In Progress
  • Assignee set to rfan1

I will add the salt test to sle staging https://openqa.suse.de/group_overview/125

Actions #21

Updated by rfan1 about 1 month ago

https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/20439

Next step,

Enable the test on sle-micro and micro-os. some code changes need to be done due to read only system.

Actions #22

Updated by rfan1 about 1 month ago

Based on https://bugzilla.suse.com/show_bug.cgi?id=1231882#c4

> ACK with RM and Architects. salt-master is not supposed to be part of any
> Micro release. If it's in 6.0 and 6.1 it's a mistake.
> Also, the positioning documents only mention salt-minion explicitly.
> 
> @Richard, feel free to disable the test for the master node. Let's think how
> we can test the minion only.

salt-master is no need to test on slem. so for now let me skip the tests on slem.

Actions #23

Updated by szarate about 1 month ago

as a follow up we can test salt-minion in masterless mode: https://test-salt.readthedocs.io/en/latest/topics/tutorials/quickstart.html

Actions #24

Updated by rfan1 about 1 month ago

  • Status changed from In Progress to Feedback
Actions #25

Updated by rfan1 23 days ago

  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF