Description of problem: The current containerized installation methods do not mount /var/log into the containerized node instance which prevents the log aggregation from working properly. Version-Release number of selected component (if applicable): Current How reproducible: Steps to Reproduce: 1. Deploy containerized OSE 2. Deploy aggregated logging components, observe failure 3. Actual results: Fluentd doesn't work because it needs read-write access to host level /var/log Expected results: Aggregated logging works properly Additional info:
reference: http://lists.openshift.redhat.com/openshift-archives/dev/2016-February/msg00069.html https://github.com/openshift/origin/pull/7398 Proposed fix : https://github.com/openshift/openshift-ansible/pull/1440
Will verify it when the bug [1] is fixed. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1309192#c9
(In reply to chunchen from comment #2) > Will verify it when the bug [1] is fixed. > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1309192#c9 Ok, I marked that one as a blocker even though I'm not really sure it's truly a blocker. I suspect this bug could be tested by running 3.1 OSE and 3.1.1 logging components.
https://bugzilla.redhat.com/show_bug.cgi?id=1309192 should have nothing to do with this issue. 1309192 deals with the Metrics components and this issue deals with the logging components. These are two separate projects and need to have separate BZ listed for them. I am removing this issue as a dependency on 1309192
(In reply to Scott Dodson from comment #0) > Fluentd doesn't work because it needs read-write access to host level > /var/log Just to set the record straight, it's the node container that needs to write things to host /var/log because that's where fluentd is looking for them. Fluentd doesn't see that any docker logs exist if node isn't writing symlinks in /var/log.
It's fixed, checked with below latest logging images: [root@openshift-154 ~]# docker images|grep logging| awk '{print $1" "$3}' |awk -F'/' '{print $2"/"$3}' openshift3/logging-elasticsearch bd98af831d62 openshift3/logging-fluentd 0acd0a966bf4 openshift3/logging-kibana 32f915bc69ad openshift3/logging-deployment 383767c6b100 openshift3/logging-auth-proxy 948429aebce9 [root@openshift-154 ~]# ps -ef |grep openshift3 |grep node root 22690 1 0 2 23 ? 00:00:35 /usr/bin/docker run --name atomic-openshift-node --rm --privileged --net=host --pid=host -v /:/rootfs:ro -e CONFIG_FILE=/etc/origin/node/node-config.yaml -e OPTIONS=--loglevel=5 -e HOST=/rootfs -e HOST_ETC=/host-etc -v /var/lib/origin:/var/lib/origin -v /etc/origin/node:/etc/origin/node -v /etc/localtime:/etc/localtime:ro -v /etc/machine-id:/etc/machine-id:ro -v /run:/run -v /sys:/sys:ro -v /usr/bin/docker:/usr/bin/docker:ro -v /var/lib/docker:/var/lib/docker -v /lib/modules:/lib/modules -v /etc/origin/openvswitch:/etc/openvswitch -v /etc/origin/sdn:/etc/openshift-sdn -v /etc/systemd/system:/host-etc/systemd/system -v /var/log:/var/log openshift3/node
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-2016:1065