Bug 1321258 - Get error ContainerCannotRun in logging deployer pod with the latest image
Summary: Get error ContainerCannotRun in logging deployer pod with the latest image
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 3.1.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: ewolinet
QA Contact: chunchen
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-25 06:06 UTC by Xia Zhao
Modified: 2016-09-30 02:16 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-12 16:34:16 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:1064 0 normal SHIPPED_LIVE Important: Red Hat OpenShift Enterprise 3.2 security, bug fix, and enhancement update 2016-05-12 20:19:17 UTC

Description Xia Zhao 2016-03-25 06:06:44 UTC
Problem description: 
The latest logging deployer image can not run because of "exec: "./run.sh": permission denied".

Version-Release number of selected component (if applicable):
The latest logging deployer image from brew:
openshift3/logging-deployment    3307201e1b75

How reproducible:
Always

Steps to Reproduce:
1. Login openshift, create a project
oc new-project logging
2. Create supporting service account and deployer secrets
oc create -f - <<API
apiVersion: v1
kind: ServiceAccount
metadata:
 name: logging-deployer
secrets:
- name: logging-deployer
API
oc secrets new logging-deployer nothing=/dev/null
oc policy add-role-to-user edit system:serviceaccount:logging:logging-deployer
#Note: need 'cluster-admin' role to run below commands
oadm policy add-scc-to-user hostmount-anyuid system:serviceaccount:logging:aggregated-logging-fluentd
oadm policy add-cluster-role-to-user cluster-reader system:serviceaccount:logging:aggregated-logging-fluentd

3. Run the deployer:
wget https://raw.githubusercontent.com/openshift/origin-aggregated-logging/master/deployment/deployer.yaml
oc process -f deployer.yaml -v IMAGE_PREFIX=${image_prefix},\
              KIBANA_HOSTNAME=${kibana_route},\
              PUBLIC_MASTER_URL=https://${master_dns}:8443,\
              ES_INSTANCE_RAM=1024M,\
              ES_CLUSTER_SIZE=1,\
              | oc create -f -
4. Check the deployer pod status

Actual Result:
Get error ContainerCannotRun in logging deployer pod
# oc get po -n logging
NAME                     READY     STATUS               RESTARTS   AGE
logging-deployer-vbo0t   0/1       ContainerCannotRun   1          6m
# oc logs -f logging-deployer-vbo0t -n !$
oc logs -f logging-deployer-vbo0t -n logging
exec: "./run.sh": permission denied

Expected Result:
Deployer pod should complete successfully

Additional info:
Issue did not happen with the previous brew image

Comment 5 Xia Zhao 2016-03-29 08:03:27 UTC
Verified with latest and 3.1.1-11 deployer images, they all can be run. This issue is fixed. Thanks!

Comment 9 errata-xmlrpc 2016-05-12 16:34:16 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/RHSA-2016:1064


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