Bug 1738412
| Summary: | The manifests for kubefed controller and webhook are not correct in the downstream kubefed-operator image | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Qin Ping <piqin> |
| Component: | Federation | Assignee: | Aniket Bhat <anbhat> |
| Status: | CLOSED ERRATA | QA Contact: | Qin Ping <piqin> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.2.0 | CC: | anbhat |
| Target Milestone: | --- | ||
| Target Release: | 4.2.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-10-16 06:35:02 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
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 |
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: