action #61901
closed
[functional][y] Check if wicked is running for yast command line tests
Added by riafarov over 4 years ago.
Updated about 4 years ago.
Category:
Enhancement to existing tests
Description
Motivation¶
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.
- Category set to Enhancement to existing tests
- Due date changed from 2020-02-11 to 2020-02-25
- Due date changed from 2020-02-25 to 2020-03-10
- Due date changed from 2020-03-10 to 2020-03-24
- Status changed from New to Workable
- Estimated time set to 2.00 h
- Status changed from Workable to In Progress
- Assignee set to ybonatakis
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/9746
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
- Status changed from In Progress to Feedback
Actually we have nothing to do on this ticket as there is already a check introduced by dbe50c9b66. This is checking if NetworkManager is the network controller and returns.
- Status changed from Feedback to Workable
- Status changed from Workable to In Progress
- Status changed from In Progress to Feedback
- Status changed from Feedback to Resolved
riafarov will create follow up ticket to make the test suite work on TW.
- Copied to action #64731: [functional][y] generate TW image with wicked and use it in yast2_cmdline and nis MM test suites added
Also available in: Atom
PDF