Description of problem: The manifests for kubefed controller and webhook are not correct in the downstream kubefed-operator image Version-Release number of selected component (if applicable): kubefed-operator image version: quay.io/openshift-release-dev/ocp-v4.0-art-dev:v4.2.0-201908061459-ose-kubefed-operator How reproducible: 100% Steps to Reproduce: 1. # podman images|grep ose-kubefed-operator quay.io/openshift-release-dev/ocp-v4.0-art-dev v4.2.0-201908061459-ose-kubefed-operator ca7463696de5 11 hours ago 296 MB 2. # podman run --rm --entrypoint /bin/sh ca7463696de5 -c 'cat /deploy/resources/controller/deployment.yaml|grep command -A 1' command: - /hyperfed/controller-manager 3. # podman run --rm --entrypoint /bin/sh ca7463696de5 -c 'cat /deploy/resources/webhook/webhook_deployment.yaml|grep command -A 1' command: - "/hyperfed/webhook" Actual results: The binary files are exist in the root dir not the hyperfed dir. When starting kubefed webhook, getting the following error: Warning Failed 14s (x6 over 76s) kubelet, ip-10-0-156-22.ap-northeast-1.compute.internal Error: container create failed: container_linux.go:336: starting container process caused "exec: \"/hyperfed/webhook\": stat /hyperfed/webhook: no such file or directory" Expected results: Additional info:
Verified with images: quay.io/openshift-release-dev/ocp-v4.0-art-dev:v4.2.0-201908081419-ose-kubefed quay.io/openshift-release-dev/ocp-v4.0-art-dev:v4.2.0-201908070857-ose-kubefed-operator
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:2922