QA » openQA Project » openQA Tests

It has to be decided yet if they should have dedicated hardware for that or they should used shared workers like the Yast team.

• systemd team has a webui: http://emerson.suse.de
• they don't have any worker machine for aarch64, ppc64le nor s390x.
• at the moment http://emerson.suse.de is also used as a x86_64 worker for qemu backend, but it is a too week machine that cannot handle the webui and x86_64 workers for the team.
• tblume has access to a s390x machine, but he needs it for debugging. Maybe we could find a way that he can use it for both, debugging and as openQA-worker-SUT.
• tblume will take care of looking for aarch64 and ppc64le and x86_64 machines in orthos. After that, we should help them know how to configure those machines as SUT for remote workers.

okurz wrote:

Hi tsaupe, as stated by SLindoMansilla in #25248#note-15 we are waiting for you to "look for machines". This is why I will assign this ticket to you assuming you will respond back when you either have found machine ressources useable for openQA workers or a question how we can help you.

I've got machines for x86_64 and ppc64le.
I've installed SLES12SP3 but need to postpone further processing, because I'm currently vacation backup for systemd and have to process high priority bugs.
I expect to continue processing next week.

mgriessmeier wrote:

@Thomas any update? :)
Need help with something?

Actually, the machines are up and running.
We could start the worker setup.
I'm just very busy with bugs and need a timeslot.
Also I'm currently using the ppc machine for reproducing bug 1092896.
Is it still possible to use the machine as reproducer after the openqa worker setup?

Hi Thomas,

Well, as long as there is no re-installation of the OS, it is possible.
Can you describe what you do to reproduce bugs there?

SLindoMansilla wrote:

Hi Thomas,

Well, as long as there is no re-installation of the OS, it is possible.
Can you describe what you do to reproduce bugs there?

I'm downloading the test image from the test run that was reported to fail and run it in virt-manager on my machine.
I can then install the testsuite and start the test manually inside this vm.
That turned out to be very convenient for debugging.

Also, when systemd is updated to a newer version, there are usually more tests added.
That means I need to adapt the testsuite package and thus need one machine for each architecture where I can start it.
I'm currently trying to get another machine for aarch64, so that I can adapt the testsuite (see latest entry in bug 1092896).

However, I don't need those machines permanently for development, so I guess the openQA setup could co-exist with my development system there.

Yes, you can definitely run VMs using libvirtd+virt-manager in parallel to openQA workers on that machine.

okurz wrote:

Yes, you can definitely run VMs using libvirtd+virt-manager in parallel to openQA workers on that machine.

Ok, so let's make an appointment for the openQA setup on my ppc64le, and x86_64 VM.
If it suits you, next week Monday or Tuesday would be fine.
For the time, I don't have preferences, just pick what is convenient for you.

Monday at 13:30?

SLindoMansilla wrote:

Monday at 13:30?

Ok, fine for me.

Status update:

remote workers configured for x86_64 and ppc64le

I'm unable to get a permanent machine reservation on an aarch64 host.
There is also a technical problem, aarch64 doesn't support virtualization nesting.
That makes the current testsuite setup for the extended tests unusable.
Looking for a solution.

For s390x, I'm still looking for a machine.

tsaupe wrote:

For s390x, I'm still looking for a machine.

Can I support you here?

mgriessmeier wrote:

tsaupe wrote:

For s390x, I'm still looking for a machine.

Can I support you here?

Sure, I'd be happy if you could give me a VM.
All orthos machines have by far too few resources for the tests.

Clarify if can solve aarch64 workers issue first.

s390x worker already working.

Only aarch64 missing. Need to research how to enable kvm virtualization for aarch64 on SLE12-SP3 or SLE15.

SR about packages needed by os-autoinst when using svirt backend (s390x, xen): https://build.opensuse.org/request/show/618317

Hi Thomas,

if I remember properly, you already got aarch64, ppc64le, s390x and x86_64 workers for your openQA instance. If so, could you resolve this ticket?

SLindoMansilla wrote:

systemd team is still missing an aarch64 worker

It seems we have insufficient machines on aarch64 to get a fixed worker slaves.
Since all the other slaves are set up, I can live with that.
If in need, I will try to use an orthos machine instead.

I'm closing the ticket therewith.