Bug 1434426
| Summary: | cns-deploy should not abort if setting up of heketi pod fails | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | krishnaram Karthick <kramdoss> |
| Component: | CNS-deployment | Assignee: | Mohamed Ashiq <mliyazud> |
| Status: | CLOSED ERRATA | QA Contact: | Tejas Chaphekar <tchaphek> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | cns-3.5 | CC: | akhakhar, annair, hchiramm, jarrpa, madam, mliyazud, mzywusko, pprakash, rcyriac, rreddy, rtalur, sselvan |
| Target Milestone: | --- | ||
| Target Release: | CNS 3.5 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | cns-deploy-4.0.0-6.el7rhgs | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-04-20 18:28:25 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: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1415600 | ||
|
Description
krishnaram Karthick
2017-03-21 13:39:18 UTC
Patch upstream https://github.com/gluster/gluster-kubernetes/pull/206 Verified the bug in cns-deploy-4.0.0-13.el7rhgs.x86_64. This issue seems to be fixed. Deleted heketi template towards the end, so heketi couldn't be setup. cns deploy did not abort as expected. A message asking admin to manually setup heketi would have been good here. will file an enhancement bug separately. =============================================================================== Do you wish to proceed with deployment? [Y]es, [N]o? [Default: Y]: y Using OpenShift CLI. NAME STATUS AGE storage-project Active 8d Using namespace "storage-project". Checking that heketi pod is not running ... OK template "deploy-heketi" created serviceaccount "heketi-service-account" created template "heketi" created template "glusterfs" created role "edit" added: "system:serviceaccount:storage-project:heketi-service-account" node "dhcp46-221.lab.eng.blr.redhat.com" labeled node "dhcp46-222.lab.eng.blr.redhat.com" labeled node "dhcp46-91.lab.eng.blr.redhat.com" labeled daemonset "glusterfs" created Waiting for GlusterFS pods to start ... OK service "deploy-heketi" created route "deploy-heketi" created deploymentconfig "deploy-heketi" created Waiting for deploy-heketi pod to start ... OK Creating cluster ... ID: 63a23110b91c538ddaf53992af5977f9 Creating node dhcp46-221.lab.eng.blr.redhat.com ... ID: 44470d27b706d89df4d50cdadc1f5783 Adding device /dev/sdf ... OK Creating node dhcp46-222.lab.eng.blr.redhat.com ... ID: 2689ec4d55a2fe725c82952baa5de6bc Adding device /dev/sdd ... OK Creating node dhcp46-91.lab.eng.blr.redhat.com ... ID: 76332f61d060cc73ad2d192634b63390 Adding device /dev/sdd ... OK heketi topology loaded. Saving heketi-storage.json secret "heketi-storage-secret" created endpoints "heketi-storage-endpoints" created service "heketi-storage-endpoints" created job "heketi-storage-copy-job" created deploymentconfig "deploy-heketi" deleted route "deploy-heketi" deleted service "deploy-heketi" deleted job "heketi-storage-copy-job" deleted pod "deploy-heketi-1-rf7sz" deleted secret "heketi-storage-secret" deleted service "heketi" created route "heketi" created deploymentconfig "heketi" created Waiting for heketi pod to start ... OK Failed to communicate with heketi service. Please verify that a router has been properly configured. =============================================================================== 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:1112 |