From Fedora Project Wiki
(sudo instead of su) |
(chrony-wait.service must be disabled otherwise chronyd.service is started by this. Enable chrony again if it was before the test.) |
||
| Line 11: | Line 11: | ||
#: {{command|sudo systemctl stop chronyd.service}} | #: {{command|sudo systemctl stop chronyd.service}} | ||
#: {{command|sudo systemctl disable chronyd.service}} | #: {{command|sudo systemctl disable chronyd.service}} | ||
#: {{command|sudo systemctl disable chrony-wait.service}} | |||
# Now reboot. Log in again, and run the following commands: | # Now reboot. Log in again, and run the following commands: | ||
#: {{command|sudo systemctl status chronyd.service}} | #: {{command|sudo systemctl status chronyd.service}} | ||
| Line 28: | Line 29: | ||
#: {{command|sudo systemctl status chronyd.service}} | #: {{command|sudo systemctl status chronyd.service}} | ||
#: {{command|ps aux <nowiki>|</nowiki> grep chronyd}} | #: {{command|ps aux <nowiki>|</nowiki> grep chronyd}} | ||
# If chrony was enabled before starting the test, then enable and start it again. | |||
#: {{command|sudo systemctl start chrony-wait.service}} | |||
#: {{command|sudo systemctl enable chronyd.service}} | |||
#: {{command|sudo systemctl start chronyd.service}} | |||
|results= | |results= | ||
# Each time they appear, the commands {{command|sudo systemctl status chronyd.service}} and {{command|ps aux <nowiki>|</nowiki> grep chronyd}} check whether the service is running. The expected results, in order, are: | # Each time they appear, the commands {{command|sudo systemctl status chronyd.service}} and {{command|ps aux <nowiki>|</nowiki> grep chronyd}} check whether the service is running. The expected results, in order, are: | ||
Latest revision as of 14:55, 9 May 2021
Associated release criterion
This test case is associated with the Basic_Release_Criteria#system-service-manipulation 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 Basic_Release_Criteria#system-service-manipulation 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 starting, stopping, enabling and disabling system services works as expected.
Setup
- Perform an installation of the Fedora release you wish to test, making as few choices as possible and making the most obvious and simple choices where choice is required
How to test
Service used for testing
You may use another service for testing if necessary. Ensure it is a service which works reliably - this is a test of the service management mechanism, not of the particular service.
You may use another service for testing if necessary. Ensure it is a service which works reliably - this is a test of the service management mechanism, not of the particular service.
- Log in to the installed system
- In a console, run the following commands:
sudo systemctl stop chronyd.servicesudo systemctl disable chronyd.servicesudo systemctl disable chrony-wait.service
- Now reboot. Log in again, and run the following commands:
sudo systemctl status chronyd.serviceps aux | grep chronydsudo systemctl start chronyd.servicesudo systemctl status chronyd.serviceps aux | grep chronydsudo systemctl stop chronyd.servicesudo systemctl status chronyd.serviceps aux | grep chronydsudo systemctl enable chronyd.service
- Now reboot. Log in again, and run the following commands:
sudo systemctl status chronyd.serviceps aux | grep chronydsudo systemctl disable chronyd.service
- Now reboot. Log in again, and run the following commands:
sudo systemctl status chronyd.serviceps aux | grep chronyd
- If chrony was enabled before starting the test, then enable and start it again.
sudo systemctl start chrony-wait.servicesudo systemctl enable chronyd.servicesudo systemctl start chronyd.service
Expected Results
- Each time they appear, the commands
sudo systemctl status chronyd.serviceandps aux | grep chronydcheck whether the service is running. The expected results, in order, are:- Disabled and inactive (not running)
- Disabled but active (running)
- Disabled and inactive (not running)
- Enabled and active (running)
- Disabled and inactive (not running)