Description of problem: When deploying clusterlogging from OperatorHub, the fluentd pods do not start. oc describe on the fluentd daemonset shows: Events: Type Reason Age From Message ---- ------ ---- ---- ------- Warning FailedCreate 4m (x23 over 39m) daemonset-controller Error creating: pods "fluentd-" is forbidden: unable to validate against any security context constraint: [spec.volumes[0]: Invalid value: "hostPath": hostPath volumes are not allowed to be used spec.volumes[1]: Invalid value: "hostPath": hostPath volumes are not allowed to be used spec.volumes[2]: Invalid value: "hostPath": hostPath volumes are not allowed to be used spec.volumes[5]: Invalid value: "hostPath": hostPath volumes are not allowed to be used spec.volumes[6]: Invalid value: "hostPath": hostPath volumes are not allowed to be used spec.volumes[7]: Invalid value: "hostPath": hostPath volumes are not allowed to be used spec.volumes[8]: Invalid value: "hostPath": hostPath volumes are not allowed to be used spec.volumes[9]: Invalid value: "hostPath": hostPath volumes are not allowed to be used spec.containers[0].securityContext.privileged: Invalid value: true: Privileged containers are not allowed] workaround: oc adm policy add-scc-to-user privileged -z logcollector Version-Release number of selected component (if applicable): 4.0.0-0.nightly-2019-02-11-045151 How reproducible: Always Steps to Reproduce: 1. Install cluster logging from OperatorHub 2. In the console, create a clusterlogging resource using the default yaml, changing the namespace to openshift-logging 3. Wait for elasticsearch and kibana pods to be Ready Actual results: no fluentd pods running. oc describe ds fluentd shows the error above. Expected results: fluentd pods running after creating a clusterlogging resource.
*** This bug has been marked as a duplicate of bug 1672772 ***