Red Hat Bugzilla – Bug 1509052
Non-Developer Deployments of Ansible Service Broker should not use log file
Last modified: 2017-11-28 17:21:23 EST
Description of problem: Since Kubernetes and OpenShift have their own logging mechanics when containers log to stdout, it is not necessary to log to file when deploying the Ansible Service Broker (except for development purposes). Steps to Reproduce: https://github.com/openshift/openshift-ansible/blob/129e91a3654943228c9ddeb38d6119a706cedcc2/roles/ansible_service_broker/tasks/install.yml#L319 Expected results: Broker should not use logfile
It's important to note that changes for this bug will only impact deployments of the Ansible Service Broker via the openshift-ansible project.
https://github.com/openshift/openshift-ansible/pull/5994
Commits pushed to master at https://github.com/openshift/openshift-ansible https://github.com/openshift/openshift-ansible/commit/d9a3b42cc832b8634f624b14cbee4f6db9345cf6 Bug 1509052 - Remove logfile from broker config https://github.com/openshift/openshift-ansible/commit/9e5462826beb7bece09e55b20f3fe47a65c8b44c Merge pull request #5994 from djzager/bz1509052-broker-logfile Bug 1509052 - Remove logfile from broker config
Fixed. openshift-ansible-3.7.0-0.196.0.git.0.27cd7ec.el7.noarch.rpm # oc get configmap broker-config -o yaml -n openshift-ansible-service-broker log: stdout: true level: info color: true openshift:
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/RHSA-2017:3188