From Fedora Project Wiki
(firewall confgiuration criterion doesn't exist any more) |
(Warn about entropy and update-testing) |
||
| Line 5: | Line 5: | ||
|setup= | |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. | # 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. | ||
# If this is a VM, be aware of this [https://fedoraproject.org/wiki/Common_F21_bugs#Rolekit_fails_to_deploy_a_Domain_Controller_on_a_VM.2C_returning_error_256 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. | |||
#* {{command|yum-config-manager --disable updates-testing }} | |||
|actions= | |actions= | ||
# Create a configuration file with the minimum required settings for the role (domaincontroller instructions can be found [https://fedorahosted.org/rolekit/wiki/DomainController here]) | # Create a configuration file with the minimum required settings for the role (domaincontroller instructions can be found [https://fedorahosted.org/rolekit/wiki/DomainController here]) | ||
Revision as of 10:23, 24 October 2014
Associated release criterion
This test case is associated with the Fedora_42_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 is associated with the Fedora_42_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.
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.
- 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.
yum-config-manager --disable updates-testing
How to test
- Create a configuration file with the minimum required settings for the role (domaincontroller instructions can be found here)
- Deploy the role with
rolectl deploy --settings-file=/path/to/configfile [--name=instancename] (rolename) - Start the role with
rolectl start (instancename) - Query the role with
rolectl status (instancename)androlectl settings (instancename) - 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 (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 stop correctly