From Fedora Project Wiki

Note.png
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.


Description

This test case tests whether starting, stopping, enabling and disabling system services works as expected.

Setup

  1. 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

Note.png
Service used for testing
You may use another service for testing if necessary (for instance, testing Fedora Cloud images remotely, where disabling sshd would prevent you accessing the system). Ensure it is a service which works reliably (like crond) - this is a test of the service management mechanism, not of the particular service.
  1. Log in to the installed system
  2. In a console, run the following commands:
    su -c 'systemctl stop sshd.service'
    su -c 'systemctl disable sshd.service'
  3. Now reboot. Log in again, and run the following commands:
    su -c 'systemctl status sshd.service'
    ps aux | grep sshd
    su -c 'systemctl start sshd.service'
    su -c 'systemctl status sshd.service'
    ps aux | grep sshd
    su -c 'systemctl stop sshd.service'
    su -c 'systemctl status sshd.service'
    ps aux | grep sshd
    su -c 'systemctl enable sshd.service'
  4. Now reboot. Log in again, and run the following commands:
    su -c 'systemctl status sshd.service'
    ps aux | grep sshd
    su -c 'systemctl disable sshd.service'
  5. Now reboot. Log in again, and run the following commands:
    su -c 'systemctl status sshd.service'
    ps aux | grep sshd

Expected Results

  1. Each time they appear, the commands su -c 'systemctl status sshd.service' and ps aux | grep sshd 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)