action #49622
Updated by JERiveraMoya about 5 years ago
## Motivation As a follow-up of #45020, a mechanism was introduced to detect wrong systemd target: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/7136/files#diff-ba06ceac413fe1a2d384ec7dd32ad033R79 Now we need to take into account all cases detected and exclude them, so we can use `asset_screen_run` or similar in case of failure, instead of info box. According to discussion in https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/7109#issuecomment-475666974 most of them has already detected: s390, hyperv, caasp/kubic, and upgrade scenario and [remote installation](https://progress.opensuse.org/issues/45020#note-24) scenario. ## Acceptance criteria * **AC1:** List of scenarios where `record_info` is displayed is elaborated. * **AC2:** Detection mechanism fails if wrong systemd target is set. ## Suggestions Perform a wide search in OSD/O3 by module (using new feature to search for modules) `installation_overview` to see if contains the record_info box. ## Further details For example, one of the scenario where we detect it: [sle-15-SP1-allmodules+allpatterns](https://openqa.suse.de/tests/2725243#step/installation_overview/28)