coordination #52949
closed
[qe-core][RPi3][epic] SLES on RaspberryPi
Added by thehejik almost 5 years ago.
Updated over 2 years ago.
Target version:
SUSE QA - Milestone 31
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¶
- 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
- Description updated (diff)
- Category set to Enhancement to existing tests
- 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
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
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
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
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
- 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.
- 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
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
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
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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
- 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
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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
- Target version changed from Milestone 28 to Milestone 31
- 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.
- 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
- Subject changed from [functional][u][RPi3] jeos-firstboot on RaspberryPi to [u][RPi3][epic] jeos-firstboot on RaspberryPi
- Description updated (diff)
- Subject changed from [u][RPi3][epic] jeos-firstboot on RaspberryPi to [u][RPi3][epic] SLES on RaspberryPi
- Description updated (diff)
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.
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.
- Description updated (diff)
- 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
- Related to action #71494: [functional][u][RPi] sporadic failures on reboot added
- Tracker changed from action to coordination
- Subject changed from [u][RPi3][epic] SLES on RaspberryPi to [qe-core][RPi3][epic] SLES on RaspberryPi
- Assignee deleted (
dheidler)
Unsassigning for now while I'm with the tools team
- 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.
- Status changed from Feedback to Resolved
Also available in: Atom
PDF