Bug 1806831
| Summary: | The operator group is not correct in the openshift-operators-redhat namespace when deploying elasticsearch-operator via console | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Qiaoling Tang <qitang> | |
| Component: | Management Console | Assignee: | Samuel Padgett <spadgett> | |
| Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> | |
| Severity: | high | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 4.4 | CC: | aos-bugs, jokerman, spadgett | |
| Target Milestone: | --- | |||
| Target Release: | 4.5.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | No Doc Update | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1807061 (view as bug list) | Environment: | ||
| Last Closed: | 2020-07-13 17:20:54 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: | 1807061 | |||
Verified with 4.5.0-0.nightly-2020-03-09-212428 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-2020:2409 |
Description of problem: For elasticsearch-operator, it's default install mode is `All namespaces on the cluster`. When deploying the EO via console, it will create a namespace named `openshift-operators-redhat` and an operator group in the openshift-operators-redhat namespace. However, the operator group doesn't support all namespaces mode. Although the EO could be deployed successfully, but it won't be copied to all namespaces on the cluster. $ oc get og -n openshift-operators-redhat -oyaml apiVersion: v1 items: - apiVersion: operators.coreos.com/v1 kind: OperatorGroup metadata: annotations: olm.providedAPIs: "" creationTimestamp: "2020-02-25T05:34:15Z" generateName: openshift-operators-redhat- generation: 1 name: openshift-operators-redhat-2nr4x namespace: openshift-operators-redhat resourceVersion: "828699" selfLink: /apis/operators.coreos.com/v1/namespaces/openshift-operators-redhat/operatorgroups/openshift-operators-redhat-2nr4x uid: d2766585-7f14-48f7-a586-2c77628c9e38 spec: targetNamespaces: - openshift-operators-redhat status: lastUpdated: "2020-02-25T05:34:15Z" namespaces: - openshift-operators-redhat kind: List metadata: resourceVersion: "" selfLink: "" example of operator group supports all namespaces: $ oc get og -n openshift-operators global-operators -oyaml apiVersion: operators.coreos.com/v1 kind: OperatorGroup metadata: creationTimestamp: "2020-02-24T07:19:37Z" generation: 1 name: global-operators namespace: openshift-operators resourceVersion: "4343" selfLink: /apis/operators.coreos.com/v1/namespaces/openshift-operators/operatorgroups/global-operators uid: 071b0f7e-ea45-4587-a480-0aca466ec3c8 status: lastUpdated: "2020-02-24T07:23:16Z" namespaces: - "" Version-Release number of selected component (if applicable): clusterversion: 4.4.0-0.nightly-2020-02-24-020331 How reproducible: Always Steps to Reproduce: 1. launch an OCP 4.4 cluster 2. deploy elasticsearch-operator via console Actual results: The elasticsearch-operator is not deployed as `All namespaces on the cluster`, so the elasticsearch pods couldn't be created in the openshift-logging namespace. Expected results: The og created by console should target to all namespaces. Additional info: