A collection of single-host tests for Atomic Host
Shell Python
Fetching latest commit…
Cannot retrieve the latest commit at this time.


Atomic Host Tests

This repo contains a number of Ansible playbooks that can be used to run tests against an Atomic Host.

The intent is to have a collection of tests that can be used to test the CentOS, Fedora, and RHEL versions of Atomic Host.

Currently, these tests fall into the category of single host, integration tests.

NOTE: This repo only provides playbooks/tests and does not currently provide any way for provisioning test resources/infrastructure.

Supported Test Suites

The following test suites are available and supported. Any other playbooks found in the repo are currently unmaintained and may not work correctly.

  • ostree admin unlock
    • Verifies the ability to install packages using ostree admin unlock
  • Docker Swarm
    • Covers the basic functionality of the docker swarm commands
  • Docker/Docker Latest
    • Validates basic docker operations using either docker or docker-latest
  • Improved Sanity Test
    • A test suite aimed at providing smoketest-like coverage of an entire Atomic Host
  • Kubernetes
    • Validates standing up a single-node Kubernetes cluster and deploying a simple web+DB application
  • Package Layering
    • Validates the package layering functionality of rpm-ostree
  • System Containers
    • Verifies the basic usage of system containers on Atomic Host
  • Runc
    • Verifies basic runc functions

Why Ansible?

The reasons for choosing Ansible playbooks are mainly 1) ease of use, 2) portability, and 3) simplicity.

  1. Ansible is a well-known tool and there is plenty of documentation available for users to rely on.

  2. Ansible requires only a small amount of functionality on the system under test (basically Python and SSH), so playbooks can be used across multiple platforms with little changes necessary.

  3. Fail fast and early. When a task in Ansible fails, the whole playbook fails (for the most part). Thus, if something fails during the execution, that is a good indication that something broke.

Running Playbooks

All the playbooks should be able to be run without any extra options on the command line. Like so:

# ansible-playbook -i inventory tests/new-tree-smoketest.main.yaml

However, some tests do accept extra arguments that can change how the test is run; please see the README for each test for details.

Additionally, certain variables are required to be configured for each test and the required variables can vary between tests. There are sensible defaults provided, but it is up to the user to configure them as they see fit.

NOTE: Playbooks are developed and tested using Ansible 2.1. Ansible 2.2 should also work, but it is not guaranteed. Please do not use any version of Ansible earlier than 2.1.


You can see how the playbooks would run by using the supplied Vagrantfile which defines multiple boxes to test with. The Vagrantfile requires a 'vagrant-reload' plugin available from the following GitHub repo:


With the plugin installed, you should be able to choose a CentOS AH box, a Fedora 24/25 AH box, or a CentOS AH Continuous (CAHC) box.

$ vagrant up centos


$ vagrant up {fedora24|fedora25}


$ vagrant up cahc

By default, the Vagrantfile will run the tests/improved-sanity-tests/main.yml playbook after Vagrant completes the provisioning of the box. The playbook which is run can be changed by setting the environment variable PLAYBOOK_FILE to point to a playbook in the repo.

$ PLAYBOOK_FILE=tests/docker-swarm/main.yml vagrant up cahc

NOTE: By default, the Vagrant boxes will provision HEAD-1 of the flavor of Atomic Host you want to bring up.