Project

General

Profile

Actions

action #105852

closed

[qe-core] Implement hardware tests for SLE RPi JeOS

Added by dheidler almost 3 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
New test
Target version:
QA (public, currently private due to #173521) - QE-Core: Ready
Start date:
2022-02-02
Due date:
% Done:

0%

Estimated time:
Difficulty:
Sprint:
QE-Core: July Sprint (Jul 06 - Aug 03)

Description

Acceptance Criteria

AC1: SLE JeOS for Raspberry Pi is tested on real hardware

Suggestions

  • We already do similar stuff for openSUSE on O3
  • Test wifi and bluetooth
Actions #1

Updated by dheidler almost 3 years ago

  • Status changed from New to In Progress
  • Assignee set to dheidler
Actions #2

Updated by dheidler almost 3 years ago

  • Category set to New test
  • Target version set to QE-Core: Ready
Actions #3

Updated by maritawerner almost 3 years ago

  • Subject changed from Implement hardware tests for SLE RPi JeOS to [qe-core] Implement hardware tests for SLE RPi JeOS
Actions #4

Updated by dheidler almost 3 years ago

  • Status changed from In Progress to Feedback
Actions #7

Updated by dheidler almost 3 years ago

allow using real serial console for bootup log: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/14175

Actions #10

Updated by dheidler almost 3 years ago

Current status here:
I planned to do the initial setup with two RPi4s (one openqa-worker and one SUT) but they are out of stock everywhere
and only available to huge prices.

So I will gather some RPi3B+ from the office and create a basic testing setup there.
They might have some problems with bluetooth so I would need to skip those test module for now.

Actions #11

Updated by szarate over 2 years ago

dheidler wrote:

Current status here:
I planned to do the initial setup with two RPi4s (one openqa-worker and one SUT) but they are out of stock everywhere
and only available to huge prices.

So I will gather some RPi3B+ from the office and create a basic testing setup there.
They might have some problems with bluetooth so I would need to skip those test module for now.

Do you need help with something here? in any case, is there something else needed for this ticket? can we close it and create "theme" story? (Multi year story)

Actions #12

Updated by dheidler over 2 years ago

There is only one thing - I already wrote about it in the last paragraph of https://confluence.suse.com/pages/viewpage.action?spaceKey=~dheidler&title=Hardware+Automation

The raspberry pi 400 that is currently the worker node doesn't have enough RAM to hold the sdcard images for all three worker instances. And I don't want to save it on the sdcard, so I'm currently using an NFS share, which is obviously slow, so it takes some time for the jobs to start, when three scdard images are copied around at the same time.

I would like to have a raspberry pi 4 with 8gb of memory to replace the raspberry pi 400 (that has only 4GB of ram), but they are currently not in stock.

Another way would be to use some old x86_64 workstation with an AP-mode compatible wifi stick and a bluetooth stick as a worker node.

Actions #13

Updated by dheidler over 2 years ago

  • Status changed from Feedback to Resolved

In the meantime I was able to order a RPi 4B with 8GB of ram.
The worker is now running on that new hardware.

Actions #14

Updated by szarate over 2 years ago

  • Sprint set to QE-Core: July Sprint (Jul 06 - Aug 03)
Actions

Also available in: Atom PDF