Bug 1391318

Summary: Logging stacks not able to start up due to can not pass parameters correctly
Product: OpenShift Container Platform Reporter: Xia Zhao <xiazhao>
Component: LoggingAssignee: ewolinet
Status: CLOSED ERRATA QA Contact: Xia Zhao <xiazhao>
Severity: high Docs Contact:
Priority: high    
Version: 3.4.0CC: aos-bugs, dma, penli, tdawson
Target Milestone: ---Keywords: Regression, TestBlocker
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-18 12:49:03 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
deployer_log none

Comment 1 Xia Zhao 2016-11-03 03:48:57 UTC
Created attachment 1216846 [details]
deployer_log

Comment 2 Xia Zhao 2016-11-03 03:50:19 UTC
Blocked ON_QA bugs verification & 3.4.0 logging tests

Comment 4 Peng Li 2016-11-03 06:32:45 UTC
This is OCP 3.4 change caused issue, now we can't pass multi parameters in a line seperated by comma,
new-app logging-deployer-template -p IMAGE_PREFIX=$PREFIX,IMAGE_VERSION=$VERSION,MODE=install

oc get dc/logging-curator -o yaml -n xiazhao
(...)
     image:
logging-curator:3.4.0,IMAGE_PREFIX_DEFAULT=brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/openshift3/
(...)

notice the image is wrong due to the OCP change.

Comment 5 Peng Li 2016-11-03 08:40:49 UTC
See https://bugzilla.redhat.com/show_bug.cgi?id=1391378

this may be caused by oc client change, from the log can see such info "oc new-app --value no longer accepts comma-separated lists of values.", and oc process -v don't support comma seperated values too now.

thus statements like https://github.com/openshift/origin-aggregated-logging/blob/master/deployer/scripts/install.sh#L405
may throw exception.

Comment 7 DeShuai Ma 2016-11-03 09:16:05 UTC
As this change https://github.com/openshift/origin/pull/11539
Need update logging repo.

Comment 9 Xia Zhao 2016-11-04 01:55:29 UTC
Verified with the latest images on brew registry, did not get the original issue reproduced anymore, set to verified.

Images tested:
brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/openshift3/logging-deployer        3.4.0               a04f34372176        6 hours ago         762.5 MB
brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/openshift3/logging-elasticsearch   3.4.0               9b9452c0f8c2        33 hours ago        407.6 MB
brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/openshift3/logging-kibana          3.4.0               7fc9916eea4d        35 hours ago        347.2 MB
brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/openshift3/logging-auth-proxy      3.4.0               0d8e3202af61        9 days ago          238.3 MB
brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/openshift3/logging-fluentd         3.4.0               22aea57e7576        9 days ago          240.3 MB
brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/openshift3/logging-curator         3.4.0               9af78fc06248        9 days ago          256.5 MB

# openshift version
openshift v3.4.0.21+ca4702d
kubernetes v1.4.0+776c994
etcd 3.1.0-rc.0

$ oc get po
NAME                          READY     STATUS             RESTARTS   AGE
logging-curator-1-4ycul       1/1       Running            1          10m
logging-deployer-0nc12        0/1       Completed          0          11m
logging-es-e1bxs3th-1-htc5i   1/1       Running            0          10m
logging-fluentd-lfml4         1/1       Running            0          10m
logging-kibana-1-hxgbc        1/2       CrashLoopBackOff   6          10m

Comment 10 ewolinet 2016-12-12 15:44:47 UTC
The deployer script was still using comma delimited parameters which was deprecated. Prerelease issue, no docs needed.

Comment 12 errata-xmlrpc 2017-01-18 12:49:03 UTC
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-2017:0066