Bug 1683701
Summary: | Clusterlogging is created but deployments not created: "system:serviceaccount:openshift-operators:cluster-logging-operator" cannot list resource "clusterloggings" | ||||||
---|---|---|---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Mike Fiedler <mifiedle> | ||||
Component: | Logging | Assignee: | Jeff Cantrill <jcantril> | ||||
Status: | CLOSED ERRATA | QA Contact: | Anping Li <anli> | ||||
Severity: | urgent | Docs Contact: | |||||
Priority: | urgent | ||||||
Version: | 4.1.0 | CC: | aos-bugs, ewolinet, mifiedle, qitang, rmeggins, xtian | ||||
Target Milestone: | --- | ||||||
Target Release: | 4.1.0 | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | No Doc Update | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2019-06-04 10:44:39 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: | |||||||
Attachments: |
|
Description
Mike Fiedler
2019-02-27 15:31:40 UTC
How are you installing the operator? It seems like you are missing the clusterloggings CRD from your system. `$ oc get crds` # oc get crd | egrep "clusterlogging|elastic" clusterloggings.logging.openshift.io 2019-02-27T13:44:51Z elasticsearches.logging.openshift.io 2019-02-27T13:44:51Z The clusterlogging CR gets created ok: # oc get clusterlogging -o wide -n openshift-logging NAME AGE instance 132m Installing the operator like this: 1. login in to the console 2. Click Catalogs -> OperatorHub 3. Click Community Operators 4. Click Cluster Logging 5. Click Install Created attachment 1539200 [details]
cluster logging install plan
Believe this will be resolved by https://github.com/operator-framework/community-operators/pull/85 Verified in 4.0.0-0.nightly-2019-03-05-065158. 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:0758 |