action #135368
Updated by rainerkoenig 8 months ago
#### Motivation The `cockpit_service` test module has a [check for NetworkManager](https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/6f7f4892dba5f59bba0e62c3078497d2010efbf6/tests/microos/cockpit_service.pm#L38) built in that makes the test fail if it runs on a distribution that should have NetworkManager installed by default. This check will cause problems when `cockpit_service` is run in a migration scenario (observed on SLE Micro 5.1->5.5 migration), because the initial version in the migration test had `wicked` installed an running and there is not automatic migration from 'wicked` to NetworkManager. So after doing `zypper_migration` we end up in a situation that the upgraded system is still running `wicked` which then will lead to a failure. #### ToDo After some discussion on Slack Change the result was to create an own YAML schedule for migration and don't use check from `cockpit_service` test because it will do more harm than good in migration scenarios. An easy fix would be to `softfail` instead of `die` so that since its checks are not really related to we record the unwanted condition, but the migration scenarios. test suite can continue. ##### Acceptance criteria **AC1**: Migration tests Test will no longer fail in the `SLE Micro/Yast and migraiton` job group will work without `cockpit_service` test. migration scenarios that come from a installation that used `wicked` for networking.