From Fedora Project Wiki
(create a service manipulation validation test case) |
(chrony-wait.service must be disabled otherwise chronyd.service is started by this. Enable chrony again if it was before the test.) |
||
(5 intermediate revisions by 4 users not shown) | |||
Line 1: | Line 1: | ||
{{Template:Associated_release_criterion|Alpha|system-service-manipulation}} | |||
{{QA/Test_Case | {{QA/Test_Case | ||
|description=This test case tests whether starting, stopping, enabling and disabling system services works as expected. | |description=This test case tests whether starting, stopping, enabling and disabling system services works as expected. | ||
Line 4: | Line 6: | ||
# 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 | # 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 | ||
|actions= | |actions= | ||
{{admon/note|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.}} | |||
# Log in to the installed system | # Log in to the installed system | ||
# In a console, run the following commands: | # In a console, run the following commands: | ||
#: {{command| | #: {{command|sudo systemctl stop chronyd.service}} | ||
#: {{command| | #: {{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| | #: {{command|sudo systemctl status chronyd.service}} | ||
#: {{command|ps aux <nowiki>|</nowiki> grep | #: {{command|ps aux <nowiki>|</nowiki> grep chronyd}} | ||
#: {{command| | #: {{command|sudo systemctl start chronyd.service}} | ||
#: {{command| | #: {{command|sudo systemctl status chronyd.service}} | ||
#: {{command|ps aux <nowiki>|</nowiki> grep | #: {{command|ps aux <nowiki>|</nowiki> grep chronyd}} | ||
#: {{command| | #: {{command|sudo systemctl stop chronyd.service}} | ||
#: {{command| | #: {{command|sudo systemctl status chronyd.service}} | ||
#: {{command|ps aux <nowiki>|</nowiki> grep | #: {{command|ps aux <nowiki>|</nowiki> grep chronyd}} | ||
#: {{command| | #: {{command|sudo systemctl enable chronyd.service}} | ||
# Now reboot. Log in again, and run the following commands: | # Now reboot. Log in again, and run the following commands: | ||
#: {{command| | #: {{command|sudo systemctl status chronyd.service}} | ||
#: {{command|ps aux <nowiki>|</nowiki> grep | #: {{command|ps aux <nowiki>|</nowiki> grep chronyd}} | ||
#: {{command| | #: {{command|sudo systemctl disable chronyd.service}} | ||
# Now reboot. Log in again, and run the following commands: | # Now reboot. Log in again, and run the following commands: | ||
#: {{command| | #: {{command|sudo systemctl status chronyd.service}} | ||
#: {{command|ps aux <nowiki>|</nowiki> grep | #: {{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| | # 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: | ||
#: Disabled and inactive (not running) | #: Disabled and inactive (not running) | ||
#: Disabled but active (running) | #: Disabled but active (running) |
Latest revision as of 14:55, 9 May 2021
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
- Log in to the installed system
- In a console, run the following commands:
sudo systemctl stop chronyd.service
sudo systemctl disable chronyd.service
sudo systemctl disable chrony-wait.service
- Now reboot. Log in again, and run the following commands:
sudo systemctl status chronyd.service
ps aux | grep chronyd
sudo systemctl start chronyd.service
sudo systemctl status chronyd.service
ps aux | grep chronyd
sudo systemctl stop chronyd.service
sudo systemctl status chronyd.service
ps aux | grep chronyd
sudo systemctl enable chronyd.service
- Now reboot. Log in again, and run the following commands:
sudo systemctl status chronyd.service
ps aux | grep chronyd
sudo systemctl disable chronyd.service
- Now reboot. Log in again, and run the following commands:
sudo systemctl status chronyd.service
ps aux | grep chronyd
- If chrony was enabled before starting the test, then enable and start it again.
sudo systemctl start chrony-wait.service
sudo systemctl enable chronyd.service
sudo systemctl start chronyd.service
Expected Results
- Each time they appear, the commands
sudo systemctl status chronyd.service
andps aux | grep chronyd
check 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)