977aaf6f59
Use pipefail in some shell commands. In this case I don't think we can really be fooled, but not a bad idea to fail if the first command errors. Change-Id: I25750c4edfe815af9e9d9ee47639b315e7133aa2
40 lines
1.3 KiB
YAML
40 lines
1.3 KiB
YAML
- hosts: all
|
|
roles:
|
|
- role: clear-firewall
|
|
- role: ensure-kubernetes
|
|
vars:
|
|
minikube_dns_resolvers:
|
|
- '1.1.1.1'
|
|
- '8.8.8.8'
|
|
kubernetes_runtime: cri-o
|
|
- role: use-buildset-registry
|
|
buildset_registry_docker_user: root
|
|
tasks:
|
|
- name: Wait for cluster to come up
|
|
command: kubectl cluster-info
|
|
register: result
|
|
until: result.rc == 0
|
|
retries: 5
|
|
delay: 30
|
|
- name: Run a local test pod
|
|
command: kubectl run --image=quay.io/zuul/quay-testimage quaytest
|
|
- name: Wait for the pod to be ready
|
|
command: kubectl wait --for=condition=Ready pod/quaytest --timeout=60s
|
|
- name: Check the output of the pod
|
|
shell: |
|
|
set -o pipefail
|
|
kubectl logs pod/quaytest | grep 'Zuul container test'
|
|
args:
|
|
executable: /bin/bash
|
|
|
|
- name: Run a remote test pod
|
|
command: kubectl run --image=docker.io/debian:testing upstream-dockertest --command -- /bin/bash -c 'echo Upstream; sleep infinity'
|
|
- name: Wait for the pod to be ready
|
|
command: kubectl wait --for=condition=Ready pod/upstream-dockertest --timeout=60s
|
|
- name: Check the output of the pod
|
|
shell: |
|
|
set -o pipefail
|
|
kubectl logs pod/upstream-dockertest | grep 'Upstream'
|
|
args:
|
|
executable: /bin/bash
|