Created attachment 1256693 [details] failure from deployer container Description of problem: Version-Release number of selected component (if applicable): OpenShift 3.3.1.15 registry.ops.openshift.com/openshift3/metrics-deployer:3.3.1 How reproducible: Unknown Steps to Reproduce: 1. Install fresh 3.3 dedicated cluster Actual results: + oc create -f templates/heapster.yaml [28/2908] template "hawkular-heapster" created Deploying the Heapster component + echo 'Deploying the Heapster component' + '[' -n '' ']' + oc process hawkular-heapster -v IMAGE_PREFIX=registry.ops.openshift.com/openshift3/,IMAGE_VERSION=3.3.1,MASTER_URL=https://kubernetes.default.svc:443,NODE_ID=nodename,METRIC_RESOLUTION=15s + oc create -f - serviceaccount "heapster" created service "heapster" created replicationcontroller "heapster" created + validate_deployment + set -e + set +x ========================= VALIDATING THE DEPLOYMENT --- validate_nodes_accessible --- --- validate_deployment_artifacts --- ======== ERROR ========= validate_deployment_artifacts: scripts/validate.sh: line 277: line[3]: unbound variable ======================== --- validate_deployed_project --- VALIDATION FAILED After failure pods running were: [root@ip-172-31-53-218 ~]# oc get pods NAME READY STATUS RESTARTS AGE hawkular-cassandra-1-gmzvh 1/1 Running 0 18m hawkular-cassandra-2-fgd6r 1/1 Running 0 18m hawkular-metrics-rmoai 1/1 Running 0 18m heapster-u29vn 1/1 Running 0 18m metrics-deployer-rowur 0/1 Error 0 19m online-volume-provisioner-1-s5dlm 1/1 Running 0 20m
The priority of this issue is very low, the components are all installed properly (in the 1/1 state). If anything this looks like a problem with the validation script. Are you sure you are using the latest 3.3.x version?
This is a duplicate issue for https://bugzilla.redhat.com/show_bug.cgi?id=1371464 and its fixed in 3.4 This error can be safely ignored, its just the validation script which has a problem with dynamically provisioned storage (which is an alpha feature in 3.3 and not supported) *** This bug has been marked as a duplicate of bug 1371464 ***