Project

General

Profile

Actions
Copy link

coordination #52949

closed

[qe-core][RPi3][epic] SLES on RaspberryPi

Added by thehejik over 5 years ago. Updated almost 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
dheidler
Category:
New test
Target version:
SUSE QA (private) - Milestone 31
Start date:
2020-09-07
Due date:
% Done:

100%

Estimated time:
42.00 h
Difficulty:

Description

Motivation

We introduced openQA tests for RPi3 (using general aarch64 QEMU workers) on SLE15-SP1 product which are using only textmode "initialization" process based on jeos-firstboot services (as other JeOSes does).

But now we started with SLE12-SP5 which is using original SLE12 method with X11 graphical yast2-firstboot service. And of course the JeOS tests are failing in openQA then, see https://openqa.suse.de/tests/2972221

So basically we would need to add support for JeOS openQA tests to be able test graphical as well as textmode image initialization methods for upcoming products like SLE12-SP5 and SLE15-SP2 and up.

There is a small chance we will switch all upcoming SLE12 images to use the textmode jeos-firstboot but it's still not clear so please stay tuned - afaerber said on 12.06.2019: I raised the topic for the PRD but am not aware of a clarification yet.

Until now tests were performed manually on milestone candidates following the instructions from https://bugzilla.suse.com/tr_show_plan.cgi?plan_id=6328

Acceptance criteria

  • AC1: Automatic testing for SLES on Raspberry Pi is covered for Tumbleweed and SLE15-SP3
  • AC2: Sub-Tasks are resolved

Further information

Subtasks 2 (0 open — 2 closed)

action #71065: [functional][u] Schedule Raspberry Pi Tests for SLE15SP3Resolveddheidler2020-09-07

Actions
action #71836: [functional][u][RPi] manual regression testsResolveddheidler2020-09-24

Actions

Related issues 1 (0 open — 1 closed)

Related to openQA Tests (public) - action #71494: [functional][u][RPi] sporadic failures on rebootResolveddheidler2020-09-18

Actions
Actions
Copy link
 #1

Updated by thehejik over 5 years ago

  • Subject changed from [y][JeOS][RPi3] Ability for testing graphical yast2-firstboot instead of jeos-firstboot (SLE15+) on RaspberryPi to [y][JeOS][RPi3] Ability for testing graphical yast2-firstboot together with textmode jeos-firstboot on RaspberryPi
Actions
Copy link
 #2

Updated by thehejik over 5 years ago

  • Description updated (diff)
  • Category set to Enhancement to existing tests
Actions
Copy link
 #3

Updated by thehejik over 5 years ago

  • Subject changed from [y][JeOS][RPi3] Ability for testing graphical yast2-firstboot together with textmode jeos-firstboot on RaspberryPi to [y][JeOS][RPi3] yast2-firstboot as well as jeos-firstboot on RaspberryPi
Actions
Copy link
 #4

Updated by okurz over 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: jeos-filesystem-RPi
https://openqa.suse.de/tests/3021402

Actions
Copy link
 #5

Updated by okurz over 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: jeos-extratest-RPi
https://openqa.suse.de/tests/3052202

Actions
Copy link
 #6

Updated by okurz over 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: jeos-extratest-RPi
https://openqa.suse.de/tests/3166240

Actions
Copy link
 #7

Updated by okurz over 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: jeos-extratest-RPi
https://openqa.suse.de/tests/3234254

Actions
Copy link
 #8

Updated by SLindoMansilla over 5 years ago

  • Subject changed from [y][JeOS][RPi3] yast2-firstboot as well as jeos-firstboot on RaspberryPi to [functional][u][y][JeOS][RPi3] yast2-firstboot as well as jeos-firstboot on RaspberryPi
  • Priority changed from Normal to High

Since I am taking care of RPI for the moment, I will also take care of its openQA tests.
To be discussed in the grooming and prioritized by PO.

Actions
Copy link
 #9

Updated by riafarov over 5 years ago

  • Subject changed from [functional][u][y][JeOS][RPi3] yast2-firstboot as well as jeos-firstboot on RaspberryPi to [functional][u][JeOS][RPi3] yast2-firstboot as well as jeos-firstboot on RaspberryPi
Actions
Copy link
 #10

Updated by okurz over 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: jeos-extratest-RPi
https://openqa.suse.de/tests/3340138

Actions
Copy link
 #11

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: jeos-extratest-RPi
https://openqa.suse.de/tests/3400118

Actions
Copy link
 #12

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: jeos-extratest-RPi
https://openqa.suse.de/tests/3452388

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #13

Updated by SLindoMansilla about 5 years ago

  • Description updated (diff)
  • Status changed from New to Workable
  • Priority changed from High to Normal
  • Target version set to Milestone 28
  • Estimated time set to 42.00 h
Actions
Copy link
 #14

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: jeos-extratest-RPi
https://openqa.suse.de/tests/3553228

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #15

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: jeos-extratest-RPi
https://openqa.suse.de/tests/3577199

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #16

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: jeos-extratest-RPi
https://openqa.suse.de/tests/3577199

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #17

Updated by mgriessmeier almost 5 years ago

  • Target version changed from Milestone 28 to Milestone 31
Actions
Copy link
 #18

Updated by SLindoMansilla over 4 years ago

  • Subject changed from [functional][u][JeOS][RPi3] yast2-firstboot as well as jeos-firstboot on RaspberryPi to [functional][u][RPi3] yast2-firstboot as well as jeos-firstboot on RaspberryPi
  • Status changed from Workable to New

RPi is not scope of JeOS team.
This ticket needs to be adapted for QSF-U.

Actions
Copy link
 #19

Updated by SLindoMansilla over 4 years ago

  • Subject changed from [functional][u][RPi3] yast2-firstboot as well as jeos-firstboot on RaspberryPi to [functional][u][RPi3] jeos-firstboot on RaspberryPi
  • Category changed from Enhancement to existing tests to New test
Actions
Copy link
 #20

Updated by SLindoMansilla over 4 years ago

  • Subject changed from [functional][u][RPi3] jeos-firstboot on RaspberryPi to [u][RPi3][epic] jeos-firstboot on RaspberryPi
  • Description updated (diff)
Actions
Copy link
 #21

Updated by SLindoMansilla over 4 years ago

  • Subject changed from [u][RPi3][epic] jeos-firstboot on RaspberryPi to [u][RPi3][epic] SLES on RaspberryPi
Actions
Copy link
 #22

Updated by SLindoMansilla over 4 years ago

  • Description updated (diff)
Actions
Copy link
 #23

Updated by maritawerner over 4 years ago

Sergio, we could add this progress ticket to the Master Test Plan as a "Level Test Plan Link" for RPi. It is at least an overview and links to Testopia? If you agee I will do that.

Actions
Copy link
 #24

Updated by SLindoMansilla over 4 years ago

maritawerner wrote:

Sergio, we could add this progress ticket to the Master Test Plan as a "Level Test Plan Link" for RPi. It is at least an overview and links to Testopia? If you agee I will do that.

Sure, I agree.

Actions
Copy link
 #25

Updated by SLindoMansilla over 4 years ago

  • Description updated (diff)
Actions
Copy link
 #26

Updated by dheidler over 4 years ago

  • Assignee set to dheidler
Actions
Copy link
 #27

Updated by dheidler over 4 years ago

  • Due date set to 2020-09-07
  • Start date changed from 2019-06-12 to 2020-09-07

Grund: Änderung an zugehörigem Ticket: #71065

Actions
Copy link
 #28

Updated by dheidler over 4 years ago

  • Related to action #71494: [functional][u][RPi] sporadic failures on reboot added
Actions
Copy link
 #30

Updated by szarate about 4 years ago

  • Tracker changed from action to coordination
Actions
Copy link
 #32

Updated by tjyrinki_suse about 4 years ago

  • Subject changed from [u][RPi3][epic] SLES on RaspberryPi to [qe-core][RPi3][epic] SLES on RaspberryPi
Actions
Copy link
 #33

Updated by dheidler over 3 years ago

  • Assignee deleted (dheidler)

Unsassigning for now while I'm with the tools team

Actions
Copy link
 #34

Updated by dheidler almost 3 years ago

  • Status changed from New to Feedback
  • Assignee set to dheidler

Is there anything left here?
It seems that all the ACs are fulfilled.
So I will close this one.

Actions
Copy link
 #35

Updated by dheidler almost 3 years ago

  • Status changed from Feedback to Resolved
Actions
Copy link

Also available in: Atom PDF