[functional][y] Check if wicked is running for yast command line tests
As per comment in https://bugzilla.novell.com/show_bug.cgi?id=1148679 Josef has stated that tests require wicked to be running, as yast2 lan in general is useful in case of wicked only.
So, executing this test with NM doesn't make sense in general.
Therefore, test should be executed with wicked setup only. Additionally, we can add such check to simplify investigation, as in case wicked is down, tests will fail.
#7 Updated by ybonatakis about 2 years ago
I have to run a negative test but i think it works just fine.
If systemctl status returns 0 then wicked is running
for any other return code die.
The funtion systemctl uses the output of the script_run. To do so
the function is called with ignore_failure enabled. With the ignore_failure disabled will call the assert_script_run and the return code might be different
#11 Updated by riafarov about 2 years ago
- Status changed from Feedback to Workable
I see that this ticket wasn't refined well. We are talking about yast cmd tests here (https://openqa.opensuse.org/tests/1166336#step/yast2_cmdline/24 ) as mentioned in the bug. So the commit you've mentioned doens't address this issue. However, we can easily reuse some parts of the code there.
#13 Updated by ybonatakis about 2 years ago
#15 Updated by riafarov about 2 years ago
https://openqa.opensuse.org/tests/overview?distri=opensuse&version=Tumbleweed&build=20200320&groupid=38 yast_ui_devel is scheduled there. Was cancelled because yast2_ncurses fails