Descriptionkrishnaram Karthick
2017-08-22 06:59:43 UTC
Description of problem:
deploy-heketi image seems to have some issue. curl of deploy-heketi url fails and as a result cns-deplopyment fails.
curl fails When manually tried on the http://<service_ip>:8080/hello
snippet of cns-deployment:
============================
Do you wish to proceed with deployment?
[Y]es, [N]o? [Default: Y]: y
Using OpenShift CLI.
NAME STATUS AGE
storage-project Active 6d
Using namespace "storage-project".
Checking for pre-existing resources...
GlusterFS pods ...
Checking status of pods matching 'glusterfs=pod':
No resources found.
Timed out waiting for pods matching 'glusterfs=pod'.
not found.
deploy-heketi pod ...
Checking status of pods matching 'deploy-heketi=pod':
No resources found.
Timed out waiting for pods matching 'deploy-heketi=pod'.
not found.
heketi pod ...
Checking status of pods matching 'heketi=pod':
No resources found.
Timed out waiting for pods matching 'heketi=pod'.
not found.
Creating initial resources ... /usr/bin/oc -n storage-project create -f /usr/share/heketi/templates/deploy-heketi-template.yaml 2>&1
template "deploy-heketi" created
/usr/bin/oc -n storage-project create -f /usr/share/heketi/templates/heketi-service-account.yaml 2>&1
serviceaccount "heketi-service-account" created
/usr/bin/oc -n storage-project create -f /usr/share/heketi/templates/heketi-template.yaml 2>&1
template "heketi" created
/usr/bin/oc -n storage-project create -f /usr/share/heketi/templates/glusterfs-template.yaml 2>&1
template "glusterfs" created
/usr/bin/oc -n storage-project policy add-role-to-user edit system:serviceaccount:storage-project:heketi-service-account 2>&1
role "edit" added: "system:serviceaccount:storage-project:heketi-service-account"
/usr/bin/oc -n storage-project adm policy add-scc-to-user privileged -z heketi-service-account
OK
Marking 'dhcp46-199.lab.eng.blr.redhat.com' as a GlusterFS node.
/usr/bin/oc -n storage-project label nodes dhcp46-199.lab.eng.blr.redhat.com storagenode=glusterfs 2>&1
node "dhcp46-199.lab.eng.blr.redhat.com" labeled
Marking 'dhcp46-203.lab.eng.blr.redhat.com' as a GlusterFS node.
/usr/bin/oc -n storage-project label nodes dhcp46-203.lab.eng.blr.redhat.com storagenode=glusterfs 2>&1
node "dhcp46-203.lab.eng.blr.redhat.com" labeled
Marking 'dhcp46-197.lab.eng.blr.redhat.com' as a GlusterFS node.
/usr/bin/oc -n storage-project label nodes dhcp46-197.lab.eng.blr.redhat.com storagenode=glusterfs 2>&1
node "dhcp46-197.lab.eng.blr.redhat.com" labeled
Deploying GlusterFS pods.
/usr/bin/oc -n storage-project process -p NODE_LABEL=glusterfs glusterfs | /usr/bin/oc -n storage-project create -f - 2>&1
daemonset "glusterfs" created
Waiting for GlusterFS pods to start ...
Checking status of pods matching 'glusterfs=pod':
glusterfs-ck8fs 1/1 Running 0 2m
glusterfs-tjr2r 1/1 Running 0 2m
glusterfs-vnzvh 1/1 Running 0 2m
OK
/usr/bin/oc -n storage-project create secret generic heketi-config-secret --from-file=private_key=/dev/null --from-file=/usr/share/heketi/templates/heketi.json --from-file=topology.json=topology.json
secret "heketi-config-secret" created
/usr/bin/oc -n storage-project label --overwrite secret heketi-config-secret glusterfs=heketi-config-secret heketi=config-secret
secret "heketi-config-secret" labeled
/usr/bin/oc -n storage-project process -p HEKETI_EXECUTOR=kubernetes -p HEKETI_ADMIN_KEY= -p HEKETI_USER_KEY= deploy-heketi | /usr/bin/oc -n storage-project create -f - 2>&1
service "deploy-heketi" created
route "deploy-heketi" created
deploymentconfig "deploy-heketi" created
Waiting for deploy-heketi pod to start ...
Checking status of pods matching 'deploy-heketi=pod':
deploy-heketi-1-sjvk4 1/1 Running 0 3m
OK
Determining heketi service URL ...
=======================================================================
[root@dhcp46-207 ~]# curl http://172.30.55.219:8080/hello
curl: (7) Failed connect to 172.30.55.219:8080; Connection refused
Version-Release number of selected component (if applicable):
cns-deploy-5.0.0-19.el7rhgs.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Deploy cns using cns-deploy
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/RHEA-2017:2881