Re: Aggregated Logging Template Fails

2016-02-23 Thread Tim Moor
:tim.m...@spring.co.nz>> Cc: "users@lists.openshift.redhat.com<mailto:users@lists.openshift.redhat.com>" mailto:users@lists.openshift.redhat.com>> Subject: Re: Aggregated Logging Template Fails Hi Tim, What version of the logging-deployment image is your logging-depl

Re: Aggregated Logging Template Fails

2016-02-23 Thread Jordan Liggitt
Fwiw, that validation is being reverted to maintain compatibility[0][1], but you should still update to the corrected template. It's not correct to to specify a different targetPort for a headless service, and if you do, it will just be ignored. [0] https://github.com/openshift/origin/pull/7495 [1

Re: Aggregated Logging Template Fails

2016-02-23 Thread Eric Wolinetz
Hi Tim, What version of the logging-deployment image is your logging-deployer.yaml file using? There was a backwards compatibility issue with the previous support-pre-template and the version of origin you're using -- it was specifying a target port for the Elasticsearch headless services which is

Aggregated Logging Template Fails

2016-02-23 Thread Tim Moor
Hey list, having a few issues with the Aggregated Logging template provided as part of the default install. When running the deployer it’s failing with the following errors. I’ve also attached a script I’ve been using to redeploy on failure as part of debugging. Archtectiure - aklkvm019.corp