From Fedora Project Wiki
m (Adamwill moved page QA:Testcase Services start to QA:Testcase base services start: Consistent test case naming is good!) |
(add a check for services removed from boot process to resolve ordering loops) |
||
| Line 8: | Line 8: | ||
# Log in to the installed system | # Log in to the installed system | ||
# In a console, run the command {{command|systemctl --all --failed}} | # In a console, run the command {{command|systemctl --all --failed}} | ||
# In a console, run the command {{command|journalctl -b | grep 'deleted to break ordering'}} | |||
|results= | |results= | ||
# All services should start properly and systemctl | # All services should start properly and systemctl should report no failed service | ||
# There should be '''NO''' messages of the type "Job foo.service/start deleted to break ordering cycle" shown by the second command; these indicate that a service was entirely thrown out from the boot process due to a dependency loop (e.g. A.service is After B.service is After C.service is After A.service; when systemd encounters such a situation it arbitrarily discards one of the services to resolve the problem). If you see such a message, check the journal manually for more detail on the loop | |||
}} | }} | ||
[[Category:Package_systemd_test_cases]] | [[Category:Package_systemd_test_cases]] | ||
[[Category:Base_Acceptance_Test_Cases]] | [[Category:Base_Acceptance_Test_Cases]] | ||
Latest revision as of 21:20, 13 July 2018
Associated release criterion
This test case is associated with the Fedora_42_Final_Release_Criteria#system-services release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the blocker bug nomination page.
This test case is associated with the Fedora_42_Final_Release_Criteria#system-services release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the blocker bug nomination page.
Description
This test case tests whether all services start properly in a default install.
Setup
- Perform an installation of the Fedora release, you wish to test, following all defaults
How to test
- Log in to the installed system
- In a console, run the command
systemctl --all --failed - In a console, run the command
journalctl -b
Expected Results
- All services should start properly and systemctl should report no failed service
- There should be NO messages of the type "Job foo.service/start deleted to break ordering cycle" shown by the second command; these indicate that a service was entirely thrown out from the boot process due to a dependency loop (e.g. A.service is After B.service is After C.service is After A.service; when systemd encounters such a situation it arbitrarily discards one of the services to resolve the problem). If you see such a message, check the journal manually for more detail on the loop