Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1395519 - logging-deployer pod failed to get started
logging-deployer pod failed to get started
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging (Show other bugs)
3.4.0
Unspecified Unspecified
medium Severity medium
: ---
: ---
Assigned To: ewolinet
Gaoyun Pei
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-11-16 00:24 EST by Gaoyun Pei
Modified: 2017-03-08 13 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-01-18 07:55:11 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0066 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.4 RPM Release Advisory 2017-01-18 12:23:26 EST

  None (edit)
Description Gaoyun Pei 2016-11-16 00:24:11 EST
Description of problem:
Enable logging deployment in ansible inventory and run the installer playbook, installation aborted when waiting for logging pod to be ready. The logging-deployer pod run into error status for not passing parameters correctly:

[root@x-master-1 ~]# oc logs --tail=3 logging-deployer-idjhm
+ oc new-app logging-pvc-dynamic-template -p NAME=logging-es1,SIZE=10Gi
warning: --param no longer accepts comma-separated lists of values. "NAME=logging-es1,SIZE=10Gi" will be treated as a single key-value pair.
error: error processing template "logging/logging-pvc-dynamic-template": Template "logging-pvc-dynamic-template" is invalid: template.parameters[1]: Required value: template.parameters[1]: parameter SIZE is required and must be specified

The lines may need update in deployer:
https://github.com/openshift/origin-aggregated-logging/blob/master/deployer/scripts/install.sh#L405
https://github.com/openshift/origin-aggregated-logging/blob/master/deployer/scripts/install.sh#L425 


Version-Release number of selected component (if applicable):
REPOSITORY                   TAG     IMAGE ID
openshift3/logging-deployer  3.4.0   b8847e716761  
openshift-ansible-3.4.26-1.git.0.882474b.el7.noarch.rpm

How reproducible:
Always

Steps to Reproduce:
1.Set logging deployment options in inventory file and run the playbook openshift_hosted_logging_deploy=true
openshift_hosted_logging_deployer_prefix=registry.x.com/openshift3/
openshift_hosted_logging_deployer_version=3.4.0
openshift_hosted_logging_storage_kind=dynamic

2. The logs of logging deployment in installation and logging-deployer pod could be found in attachment


Actual results:
[root@x-master-1 ~]# oc get pod
NAME                     READY     STATUS    RESTARTS   AGE
logging-deployer-idjhm   0/1       Error     0          1h


Expected results:
logging deploy could be completed

Additional info:
Comment 6 Gaoyun Pei 2016-11-18 01:10:42 EST
Verify this bug with latest 3.4.0 logging-deployer image, id acad3da7b4ad

Trigger a same logging deployment with dynamic pv enabled, this issue have been fixed.

+ oc new-app logging-pvc-dynamic-template -p NAME=logging-es1 -p SIZE=10Gi
--> Deploying template "logging/logging-pvc-dynamic-template" to project logging

     logging-pvc-dynamic-template
     ---------
     Template for deploying logging support entities: dynamically provisioned persistentvolumeclaims.

     * With parameters:
        * NAME=logging-es1
        * SIZE=10Gi

--> Creating resources ...
    persistentvolumeclaim "logging-es1" created
--> Success
    Run 'oc status' to view your app.
Comment 7 ewolinet 2016-12-12 10:50:15 EST
Prerelease issue due to the deployer using comma delimited parameters, no docs needed.
Comment 9 errata-xmlrpc 2017-01-18 07:55:11 EST
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

Note You need to log in before you can comment on or make changes to this bug.