From Fedora Project Wiki

Revision as of 13:58, 16 September 2015 by Sgallagh (talk | contribs) (Rework role testing to match 0.4.0/F23+ style)

Associated release criterion
This test case is associated with the Fedora_36_Beta_Release_Criteria#roles 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 checks that a Rolekit role can be successfully enabled, started and queried after a Fedora Server installation, as required in the Server/Technical_Specification.


  1. Install the Fedora Server release you wish to test, in graphical or text mode, making as few choices as possible and making the most simple and obvious choices where a choice is required.
    1. Note: disable updates-testing in anaconda
  2. If this is a VM, be aware of this Common Bug about available entropy.
  3. Disable the updates-testing repository for this test, as rolekit always performs an update and may get unsafe packages from that repository. We need to test the stable repo only.
    • dnf config-manager --disable updates-testing

How to test

  1. Deploy the role with rolectl deploy (rolename) --name=instancename
  2. Query the role with rolectl status (instancename) and rolectl settings (instancename)
  3. Run rolectl sanitize (instancename) and then rolectl settings (instancename) to verify that passwords have been removed.
  4. If possible, attempt to interact with the role in expected ways - for example, if it is a database server, attempt to connect to it and create a database
  5. Stop the role with rolectl stop (instancename)
  6. Decommission the role with rolectl decommission (instancename)

Expected Results

  1. Role deployment must complete successfully
  2. The deployed role must start successfully
  3. Typical basic interaction with the deployed role must work correctly
  4. The deployed role must report its status and configuration settings correctly
  5. The deployed role must not report password data in settings after being sanitized
  6. The deployed role must stop correctly
  7. The deployed role must decommission correctly and not leave anything behind that prevents a new deployment.