QA » openQA Project » openQA Tests

also in https://openqa.opensuse.org/tests/751361#step/yast2_lan_restart/23

same for TW now https://openqa.opensuse.org/tests/753439#step/yast2_network_settings/7 , no needs to be Leap 15.1+ specific.

could it be that yast2_lan_restart in https://openqa.opensuse.org/tests/753633#step/yast2_lan_restart/14 has the same problem?

okurz wrote:

could it be that yast2_lan_restart in https://openqa.opensuse.org/tests/753633#step/yast2_lan_restart/14 has the same problem?

I thought so. And I found another one https://openqa.opensuse.org/tests/753961#step/yast2_lan_hostname/7

PR - Unschedule yast2_lan_restart_devices when Network Manager

PR - Unschedule yast2_lan_restart_devices when Network Manager-2nd try (I thought it will be easy the condition :( but it was not so straightforward, it needed more love :) )

This example that you mentioned is outdated, I am ignoring Leap during last days, unfortunately I cannot get the parent image not even retrigering like other times I did as the qcows disappear really fast and end up failing in some zypper that cannot get stuff from current build.
The logic for the warning should be ok also for Leap as it is working for TW. "yast2-lan-ui", I am not expecting any difference and the solution in code I think should intercept this warning. If some needle is missing I can create on the fly in prod as the build arrives for Leap 15.1.