openshift-ansible: cockpit/kubernetes-image no longer available from dockerhub

Description

On a fresh cluster-installation the playbooks fail at the docker_image_availability-step. Reason for this issue is, that the cockpit/kubernetes:latest image is deleted. It looks like the work on this image ist discontinued. See also https://github.com/cockpit-project/cockpit/commit/37aa31e58f3375feafdfa87d66ac8a494148b418

Version

* Your ansible version per `ansible --version`
ansible 2.9.4
  config file = None
  configured module search path = ['/home/ansible/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python3.7/site-packages/ansible
  executable location = /usr/bin/ansible
  python version = 3.7.5 (default, Oct 17 2019, 12:25:15) [GCC 8.3.0]

* The output of `git describe`
openshift-ansible-3.11.174-1

Steps To Reproduce

Just follow the instruction to install any sort of cluster

Expected Results

A working Cluster in initial state

Observed Results

     One or more checks failed
      check "docker_image_availability":
                One or more required container images are not available:
                    docker.io/cockpit/kubernetes:latest
                Checked with: skopeo inspect [--tls-verify=false] [--creds=<user>:<pass>] docker://<registry>/<image>

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 25 (1 by maintainers)

Most upvoted comments

I’ve uploaded a recent cockpit/kubernetes image to my personal namespace on dockerhub.

With the following line in your inventory, you can deploy a cluster with a working registry-console:

openshift_cockpit_deployer_image='docker.io/timbordemann/cockpit-kubernetes:latest'

Btw: This seems to be the most recent source, if you want to build the image yourself: https://github.com/cockpit-project/cockpit/tree/195.6/containers/kubernetes

+18

timbrd on Mar 5, 2020

@aroute Yes, you can use the image from @timbrd and put it in your deployment for the registry-console

pgress on Mar 5, 2020

Checking the code if I’m wrong please correct me

defaults/main.yml file will have

openshift_health_check_required_images: "{{ [] + l_required_node_images + l_cockpit_images + l_master_required_images + l_etcd_required_images + l_atomic_node_required_images }}"

l_cockpit_images var is evaluated two lines before with a ternary

l_cockpit_images: "{{ (openshift_hosted_manage_registry_console | bool) | ternary([openshift_cockpit_deployer_image], []) }}"

so as a quick workaround openshift_hosted_manage_registry_console=false at inventory file is enough for a basic installation

different configs should need to be checked accordingly, tested and worked as expected on my side but with that approach openshift install will continue to check everything apart cockpit

really not aware that this should be handled like a var setup at inventory or the code should be changed

js-max on Mar 4, 2020