User:Miabbott/QA/AtomicTests/Oc Cluster Up

Description

This testcase ensures it's possible to get an OpenShift Cluster running using 'oc cluster up'

Prerequisite
This testcase assumes you have already ran the boot test.

Setup

1. Ensure you have a booted working Atomic Host

How to test

1. Install 'origin-clients'

# rpm-ostree install origin-clients

1. Reboot the host
2. Configure insecure registries for docker by editing /etc/containers/registries.conf and adding the CIDR range '172.30.0.0/16' under the 'registries.insecure' section:

  # This is a system-wide configuration file used to
  # keep track of registries for various container backends.
  # It adheres to TOML format and does not support recursive
  # lists of registries.

  # The default location for this configuration file is /etc/containers/registries.conf.

  # The only valid categories are: 'registries.search', 'registries.insecure',
  # and 'registries.block'.

  [registries.search]
  registries = ['docker.io', 'registry.fedoraproject.org', 'registry.access.redhat.com']

  # If you need to access insecure registries, add the registry's fully-qualified name.
  # An insecure registry is one that does not have a valid SSL certificate or only does HTTP.
  [registries.insecure]
  registries = ['172.30.0.0/16']


  # If you need to block pull access from a registry, uncomment the section below
  # and add the registries fully-qualified name.
  #
  # Docker only
  [registries.block]
  registries = []

1. Restart the 'registries' and 'docker' services

 # systemctl restart registries docker

1. Use 'oc cluster up' to get the OpenShift Origin cluster running

# oc cluster up

1. You should see some output similar to this:

# oc cluster up

1. Login as the administrator

 # oc login -u system:admin

1. Switch to 'default' project

 # oc project default

1. Get the 'status' and all the components

Expected Results

1. Step #1 completes without error
2. The system boots into runlevel 5
3. Program completes with exit code 0