Description of problem: Create the separate bug to track logging part issue for https://bugzilla.redhat.com/show_bug.cgi?id=1309192#c9 . Version-Release number of selected component (if applicable): openshift3/logging-deployment 74de3e4b37f8 openshift3/logging-auth-proxy a28d3494ea25 openshift3/logging-fluentd 581e80e4e569 openshift3/logging-kibana 1d7701631584 openshift3/logging-elasticsearch 338955b2e0fd How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Should deploy EFK stack successfully. Additional info:
Yes, upstream validation got a little stricter and our usage in the template is now flagged. The deployer pod needs to be rebuilt with the new template as modified in https://github.com/openshift/origin-aggregated-logging/pull/55/files I think it may be possible to workaround by oc editing the logging-es{,-ops} services and just removing the "targetPort: cluster" line. I can't remember if deployment failed or the service just didn't work. Eric, can you follow up and build updated OSE images?
Looks like it's already under way in https://trello.com/c/MAsbhK7O/206-1-update-enterprise-logging-images-for-3-2
This should already be resolved as of last night's puddle update per the deployer image 3.2.0.1
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
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-2016:1064