Bug 1680504
Summary: | Log collector is not deployed because of "Failure creating Log collector cluster-reader role binding" | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Qiaoling Tang <qitang> |
Component: | Logging | Assignee: | Jeff Cantrill <jcantril> |
Status: | CLOSED ERRATA | QA Contact: | Anping Li <anli> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.1.0 | CC: | aos-bugs, ecordell, jcantril, mifiedle, mkhan, nstielau, pweil, qitang, rmeggins, sponnaga |
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:27 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
Qiaoling Tang
2019-02-25 08:31:04 UTC
Encounter same error when using rsyslog as log collector. Please share the instructions you use for deploying logging via community operators. For me, the workflow for installing via community operators is blocked by bz 1679309. The Operator Hub functionality in the UI keeps going away before I can get the operator installed. Normally the flow is: 1. login to console 2. Catalog -> OperatorHub 3. Show Community Operators -> Cluster Logging 4. Install and wait for the operator to show up in openshift-operators namespace. But, broken for me on 4.0.0-0.nightly-2019-02-26-125216 Is there a way to install logging from community operators without mouse clickety-clack on a UI i.e. using cli? @mike You may hit the OLM bug https://bugzilla.redhat.com/show_bug.cgi?id=1679309. @qitang, the block are updated. Well, https://github.com/operator-framework/community-operators/pull/112 is on hold. Copying in the entire cluster-reader definition into the CSV for cluster-logging-operator is too fragile to be accepted because the definition of cluster-reader changes quite often. I also attempted to request support for being able to specify the roleRef: cluster-reader in the CSV: https://github.com/operator-framework/operator-lifecycle-manager/issues/732 - but apparently OLM already supports this, but not https://github.com/operator-framework/community-operators - I'm waiting for clarification from Evan about what he meant by this before I file an issue against https://github.com/operator-framework/community-operators In the meantime, we have no other choice but to begin the process of figuring out exactly what rbac rules are needed by fluentd, and therefore cluster-logging-operator. I'll be working on this. As far as TestBlocker goes, I've been able to workaround the problem by manually adding cluster-reader to cluster-logging-operator. Copy the lines from here to the end of the file to a file: https://github.com/openshift/cluster-logging-operator/blob/master/manifests/04-role-binding.yaml#L46 Then - oc create -f file.yaml Then fluentd should be able to start. Test bolcked by https://bugzilla.redhat.com/show_bug.cgi?id=1683701 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 |