| Summary: | Failed to deploy EFK stack | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | chunchen <chunchen> |
| Component: | Logging | Assignee: | Luke Meyer <lmeyer> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | chunchen <chunchen> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 3.2.0 | CC: | aos-bugs, wsun |
| Target Milestone: | --- | Keywords: | Regression, TestBlocker |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-04-08 15:15:05 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: | |
Created attachment 1144555 [details]
deployer logs
Worked in Origin :( I will fix it, thanks. Do you need the insecureRepository annotation if you run oc import-image --insecure? This should be fixed. I smoke tested the install at least. The oc import-image --insecure --all doesn't work quite as I would have thought. Oddly, it imports about 4 out of 42 tags, and not the ones I wanted. It will get them if you're explicit though: for is in `oc get is -o name`; do oc import-image $is:3.1.1 --insecure; done After import images with "oc import-image $is:$version --insecure", the efk stack are running like below, so mark it as verified. [chunchen@F17-CCY scripts]$ oc get pod NAME READY STATUS RESTARTS AGE logging-deployer-7lwgo 0/1 Completed 0 11m logging-es-0r3ry61g-1-0m25m 1/1 Running 0 10m logging-fluentd-1-ol73p 1/1 Running 0 9m logging-kibana-1-rhrqc 2/2 Running 0 11s Thanks for verifying. Since this bug wasn't shipped, closing. |
Description of problem: It's failed to deploy EFK stack due to failed to create replication controllers for Kibana, ES and Fluentd components, and met errors 'unknown parameter name "IMAGE_PREFIX_DEFAULT"' in deployer pod logs. Version-Release number of selected component (if applicable): openshift v3.2.0.11 kubernetes v1.2.0-36-g4a3f9c5 etcd 2.2.5 openshift3/logging-deployment 3.2.0 9f5c6a1a0de4 openshift3/logging-deployment 3.1.1-13 49a140492ccc How reproducible: always Steps to Reproduce: 1. Login openshift, create a project oc new-project chunchen 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 #Login master node and run below commands: oadm policy add-role-to-user edit system:serviceaccount:chunchen:logging-deployer oadm policy add-scc-to-user privileged system:serviceaccount:chunchen:aggregated-logging-fluentd oadm policy add-cluster-role-to-user cluster-reader system:serviceaccount:chunchen:aggregated-logging-fluentd 3. Go back to oc client command line, make sure you are in 'chunchen' project, then run the deployer: oc process openshift//logging-deployer-template -v IMAGE_PREFIX=${image_prefix},\ KIBANA_HOSTNAME=${kibana_route},\ PUBLIC_MASTER_URL=https://${master_dns}:8443,\ ES_INSTANCE_RAM=1024M,\ ES_CLUSTER_SIZE=1,IMAGE_VERSION=3.2.0\ | oc create -f - 4. Wait for deployer pod completed oc get pods 5. Check the replication controllers for EFK stack oc get rc 6. Check the image streams oc get is Actual results: step 4: NAME READY STATUS RESTARTS AGE logging-deployer-a1773 0/1 Completed 0 17m step 5: return empty step 6: NAME DOCKER REPO TAGS UPDATED logging-auth-proxy registry.access.redhat.com/openshift3/ose-logging-auth-proxy 3.2.0,latest logging-elasticsearch registry.access.redhat.com/openshift3/ose-logging-elasticsearch 3.2.0,latest logging-fluentd registry.access.redhat.com/openshift3/ose-logging-fluentd 3.2.0,latest logging-kibana registry.access.redhat.com/openshift3/ose-logging-kibana 3.2.0,latest Expected results: Should create replication controllers for EFK stack and deploy successfully. Additional info: Please refer to the logs of deployer pod in attachment.