Fix functional test job

* Pin minikube to 1.22.0

Version 1.23.0 is failing with
  error: unable to recognize "deploy/crds/zuul-ci_v1alpha2_zuul_crd.yaml":
    no matches for kind "CustomResourceDefinition" in version ""

Until we learn more, pin to the previously working k8s version.

* Add debug log-level to the podman login test command

This change should improve the test failure debugging where it
currently may just prints "Shutting down, got signal: Terminated".

* Remove "https://" from registry login

Added path-based authentication to "podman login" which they argue
is incompatible with including https:// in the registry identifier.
Doing so now produces an error.

Co-Authored-By: Tristan Cacqueray <>
Change-Id: Ic44b56a2eb6ac15cc5f4af5312fa4e3956d6e457
This commit is contained in:
James E. Blair 2021-09-07 17:20:40 -07:00
parent abf47aba32
commit 5bf96c1e30
2 changed files with 2 additions and 1 deletions

View File

@ -11,6 +11,7 @@
# see:
docker_userland_proxy: false
container_runtime: docker
minikube_version: v1.22.0 # NOTE(corvus): 1.23.0 failed with no matches for kind "CustomResourceDefinition" in version ""
- job:
description: Operator integration tests with Kubernetes

View File

@ -11,7 +11,7 @@
- name: test-registry
command: ['podman', 'login', '--tls-verify=false', 'https://zuul-registry/', '-u', 'testuser', '-p', 'testpass']
command: ['podman', '--log-level=debug', 'login', '--tls-verify=false', 'zuul-registry', '-u', 'testuser', '-p', 'testpass']
privileged: true
restartPolicy: Never