Bug 1733490
Summary: | install kubefed operator failed with the downstream 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: | urgent | ||
Version: | 4.2.0 | CC: | anbhat |
Target Milestone: | --- | Keywords: | TestBlocker |
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:33:49 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: |
Description
Qin Ping
2019-07-26 08:49:47 UTC
I think the CSV you are using to install is coming from community-operators repo. I ran in to this as well. The thing to make sure before installing the operator from your catalog source is deleting the community operators catalog source. It seems like the Kubefed Operator CSV from that catalog source happily steps on the custom one. Notice how the CSV that is applied doesn’t have the KubeFedWebhook CRD. MacBook-Pro:ping_config anbhat$ oc get csv kubefed-operator.v0.1.0 -n federation-system -o yaml | grep -i KubeFedWebHook MacBook-Pro:ping_config anbhat$ Hi Aniket, I tried with the latest kubefed-operator manifests(release-4.2, commit 3725e11bd13a90238a8b3084a3e10fd5699d7835). It can work well with the ose-kubefed-oeprator:v4.2.0 downstream image well. So, I'll mark the bug as verified. 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 |