Description of problem: Cluster Logging Operator is missing appropriate RBAC definitions to be able to create the metadata-reader cluster role for log collection. Version-Release number of selected component (if applicable): 4.1.0 How reproducible: Always Steps to Reproduce: 1. Configure the ClusterLogging CR to deploy Fluentd 2. Deploy Cluster Logging Operator 3. Tail Cluster Logging Operator logs and observe error message Actual results: Fluentd daemonsets can't be created due to missing RBAC Expected results: Fluentd daemonset is able to be created Additional info:
Can someone summarize the impact of this bug? If this is not fixed in 4.1.0, is it even possible to deploy the logging stack? It sounds like no.
QE did hit this issue using the latest origin and downstream images. @eric, What is the clusterversion and CLO Operator version? Cluster version is 4.1.0-0.nightly-2019-05-14-202907 Orign: openshift/origin-cluster-logging-operator:latest Downstream: openshift/ose-cluster-logging-operator:v4.1.0-201905132354
I hit this using a local build from master (release-4.1) for CLO deployed using the manifest csv 4.1.0.
it is just specific to CI. If you deploy via OLM following the use guide. you won't hit this issue. It is Ok to move to v4.1.z
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:1635