
The commit adds integration test that includes baremetal operator - test is driven by airshipctl phases - Deploys BMO from airshipctl repository as a phase - Verifies that after VINO-CR is deployed BMHs are created - Verifies that BMO can install an image into those BMHs using pxe - Various fixes that allow to integrate with BMO - Disables password authentication for BMHs untill we have a fix - BMO fails to authenticate against simple auth provided by nginx - Removes unit-tests for BMO creation. The whole approach of requesting VMs from vino-builder should be changed. When we have final view of the process, we will well define vino-builder API and add unit-tests to vino controller and builder Change-Id: I51976ca20811b227ecb069c4ffd81d8afe086e57
27 lines
831 B
Bash
27 lines
831 B
Bash
#!/bin/sh
|
|
|
|
set -xe
|
|
|
|
# Name of the daemonset
|
|
: ${DAEMONSET_NAME:="default-vino-test-cr"}
|
|
# Namespace of the daemonset
|
|
: ${DAEMONSET_NAMESPACE:="vino-system"}
|
|
# Maximum retries
|
|
: ${MAX_RETRY:="30"}
|
|
# How long to wait between retries in seconds
|
|
: ${RETRY_INTERVAL_SECONDS:="2"}
|
|
|
|
echo "Verifying that daemonset ${DAEMONSET_NAME} created in namespace ${vino-system} exists" >&2
|
|
count=0
|
|
until kubectl --context "${KCTL_CONTEXT}" -n "${DAEMONSET_NAMESPACE}" get ds "${DAEMONSET_NAME}" >&2; do
|
|
count=$((count + 1))
|
|
if [ "${count}" -eq "${MAX_RETRY}" ]; then
|
|
echo 'Timed out waiting for daemonset to exist' >&2
|
|
exit 1
|
|
fi
|
|
echo "Retrying to get daemonset attempt ${count}/${MAX_RETRY}" >&2
|
|
sleep "${RETRY_INTERVAL_SECONDS}"
|
|
done
|
|
|
|
echo "Succesfuly verified that daemonset ${DAEMONSET_NAMESPACE}/${DAEMONSET_NAME} exists" >&2
|