QA (public) » openQA Project (public) » openQA Infrastructure (public)

ok, anything we could do? Or what do you plan as next step? As long as you are assigned I will keep the target version "future" to communicate that the SUSE QA Tools team is not actively working on this ticket.

okurz wrote:

ok, anything we could do? Or what do you plan as next step? As long as you are assigned I will keep the target version "future" to communicate that the SUSE QA Tools team is not actively working on this ticket.

tbh, I do not know what would be the next step here.

ok, let's see: So do you agree that this is likely a performance regression since we upgraded to openSUSE Leap 15.2? Do we need another bugreport for qemu or any generic bug report? Should we rollback any changes? If there is nothing else then at least I will monitor the situation how often and when these issues happen and have an automatic retrigger of these cases. Maybe when it happens not that often and we retrigger automatically there is nothing else to be done.

Using https://raw.githubusercontent.com/os-autoinst/scripts/master/openqa-query-for-job-label and calling
openqa-query-for-job-label 73297 I get:

1475717|2020-11-16 16:50:23|done|incomplete|kubeadm|backend died: Virtio terminal and svirt serial terminal do not support send_key. Use|openqa-aarch64
1469631|2020-11-13 08:13:30|done|incomplete|kubeadm|backend died: Virtio terminal and svirt serial terminal do not support send_key. Use|openqa-aarch64
1468939|2020-11-12 23:39:24|done|incomplete|upgrade_Leap_15.0_kde|backend died: Migrate to file failed, it has been running for more than 240 seconds at /usr/lib/os-autoinst/backend/qemu.pm line 267.|openqa-aarch64
1469001|2020-11-12 23:38:53|done|incomplete|upgrade_Leap_15.2_gnome|backend died: Migrate to file failed, it has been running for more than 240 seconds at /usr/lib/os-autoinst/backend/qemu.pm line 267.|openqa-aarch64
1467645|2020-11-12 01:17:58|done|incomplete|kubeadm|backend died: Virtio terminal and svirt serial terminal do not support send_key. Use|openqa-aarch64
1465574|2020-11-09 18:06:06|done|incomplete|kubeadm|backend died: Virtio terminal and svirt serial terminal do not support send_key. Use|openqa-aarch64
1465552|2020-11-09 16:51:24|done|incomplete|kubeadm|backend died: Virtio terminal and svirt serial terminal do not support send_key. Use|openqa-aarch64
1464795|2020-11-09 14:20:27|done|incomplete|microos|backend died: Virtio terminal and svirt serial terminal do not support send_key. Use|openqa-aarch64
1464792|2020-11-09 14:05:00|done|incomplete|kubeadm|backend died: Virtio terminal and svirt serial terminal do not support send_key. Use|openqa-aarch64
1465434|2020-11-09 13:30:05|done|incomplete|kubeadm|backend died: Virtio terminal and svirt serial terminal do not support send_key. Use|openqa-aarch64

so this is very much a recurring issue.

@ggardet_arm I think a "rollback" of the migration comes a bit late by now. This seems to be a clear performance regression for me but I would not now what is wrong with the code that we maintain. Unless you already have according bug reports for that please make sure to report them for whatever you consider the relevant component. I trust that you are much more of an expert regarding the aarch64 specifics here.