Bug 1735524
| Summary: | The manifests for kubefed operator in operator hub is not the right manifests for openshift 4.2 | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Qin Ping <piqin> |
| Component: | Federation | Assignee: | Paul Morie <pmorie> |
| Status: | CLOSED WONTFIX | QA Contact: | Qin Ping <piqin> |
| Severity: | medium | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 4.2.0 | CC: | anbhat, aos-bugs, jokerman, vlaad |
| 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-09-10 16:02:50 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1731845 | ||
Description of problem: The manifests for kubefed operator in operator hub is not the right manifests for openshift 4.2 Version-Release number of selected component (if applicable): $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.2.0-0.nightly-2019-08-01-014523 True False 37m Cluster version is 4.2.0-0.nightly-2019-08-01-014523 $ oc get csv -n federation-system NAME DISPLAY VERSION REPLACES PHASE kubefed-operator.v0.1.0 Kubefed Operator 0.1.0 Succeeded $ oc logs kubefed-operator-9764766df-wzqm6 -n federation-system {"level":"info","ts":1564629459.7600253,"logger":"cmd","msg":"Go Version: go1.12.5"} {"level":"info","ts":1564629459.7600615,"logger":"cmd","msg":"Go OS/Arch: linux/amd64"} {"level":"info","ts":1564629459.7600694,"logger":"cmd","msg":"Version of operator-sdk: v0.7.0+git"} How reproducible: 100% Steps to Reproduce: 1. Log into web console 2. Install the kubefed operator(operators->operatorhub) 3. Check the installation Actual results: 1. No KubeFedWebHook crd is created. 2. It's kubefed-operator 0.1.0 package Expected results: Put the right kubefed-operator 4.2 package to operator hub Additional info: