From Fedora Project Wiki
(instancename -> rolename/instancename) |
(move to obsolete test cases) |
||
| Line 1: | Line 1: | ||
{{ | {{admon/note|Obsolete|As of Fedora 29, rolekit has been deprecated. For server deployment test cases that cover the previously implemented server roles, see [[QA:Testcase_freeipa_trust_server_installation]] and [[QA:Testcase_postgresql_server_installation]].}} | ||
{{QA/Test_Case | {{QA/Test_Case | ||
| Line 25: | Line 25: | ||
# The deployed role must decommission correctly and not leave anything behind that prevents a new deployment. | # The deployed role must decommission correctly and not leave anything behind that prevents a new deployment. | ||
}} | }} | ||
[[Category: | [[Category:Obsolete_Test_Cases]] | ||
[[Category:Package_rolekit_test_cases]] | [[Category:Package_rolekit_test_cases]] | ||
Latest revision as of 23:15, 17 July 2018
Obsolete
As of Fedora 29, rolekit has been deprecated. For server deployment test cases that cover the previously implemented server roles, see QA:Testcase_freeipa_trust_server_installation and QA:Testcase_postgresql_server_installation.
As of Fedora 29, rolekit has been deprecated. For server deployment test cases that cover the previously implemented server roles, see QA:Testcase_freeipa_trust_server_installation and QA:Testcase_postgresql_server_installation.
Description
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.
Setup
- 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.
- Note: disable updates-testing in anaconda
- If this is a VM, be aware of this Common Bug about available entropy.
- 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 --set-disabled updates-testing
How to test
- Deploy the role with
rolectl deploy (rolename) --name=instancename - Query the role with
rolectl status (rolename/instancename)androlectl settings (rolename/instancename) - Run
rolectl sanitize (rolename/instancename)and thenrolectl settings (rolename/instancename)to verify that passwords have been removed. - 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
- Stop the role with
rolectl stop (rolename/instancename) - Decommission the role with
rolectl decommission (rolename/instancename)
Expected Results
- Role deployment must complete successfully
- The deployed role must start successfully
- Typical basic interaction with the deployed role must work correctly
- The deployed role must report its status and configuration settings correctly
- The deployed role must not report password data in settings after being sanitized
- The deployed role must stop correctly
- The deployed role must decommission correctly and not leave anything behind that prevents a new deployment.