Bug 1483038 - cns-deployment fails at deploy-heketi phase
Summary: cns-deployment fails at deploy-heketi phase
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: cns-deploy-tool
Version: cns-3.6
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: CNS 3.6
Assignee: Raghavendra Talur
QA Contact: krishnaram Karthick
URL:
Whiteboard:
Depends On: 1483852
Blocks: 1445448
TreeView+ depends on / blocked
 
Reported: 2017-08-18 16:15 UTC by krishnaram Karthick
Modified: 2018-12-06 19:43 UTC (History)
10 users (show)

Fixed In Version: cns-deploy-5.0.0-19
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-10-11 07:12:11 UTC
Embargoed:


Attachments (Terms of Use)
cns-deploy logs (2.66 KB, text/plain)
2017-08-18 16:16 UTC, krishnaram Karthick
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:2881 0 normal SHIPPED_LIVE cns-deploy-tool bug fix and enhancement update 2017-10-11 11:11:43 UTC

Description krishnaram Karthick 2017-08-18 16:15:02 UTC
Description of problem:
cns-deployment fails while trying to deploy deploy-heketi pod. There seems to be an error with "can't read heketi.json.template: No such file or directory". Please refer the attachment for cns-deploy logs.

snippet of cns-deploy output:
==============================
role "edit" added: "system:serviceaccount:storage-project:heketi-service-account"
node "dhcp47-23.lab.eng.blr.redhat.com" labeled
node "dhcp47-69.lab.eng.blr.redhat.com" labeled
node "dhcp46-11.lab.eng.blr.redhat.com" labeled
daemonset "glusterfs" created
Waiting for GlusterFS pods to start ... OK
sed: can't read heketi.json.template: No such file or directory
secret "heketi-config-secret" created
service "deploy-heketi" created
route "deploy-heketi" created
deploymentconfig "deploy-heketi" created
Waiting for deploy-heketi pod to start ... pods not found.
Error from server (NotFound): services "heketi" not found
serviceaccount "heketi-service-account" deleted
secret "heketi-config-secret" deleted
deploymentconfig "deploy-heketi" deleted
route "deploy-heketi" deleted
service "deploy-heketi" deleted
pod "deploy-heketi-1-8gd82" deleted

[root@dhcp47-57 ~]# oc logs deploy-heketi-1-8gd82
ERROR: Unable to parse /etc/heketi/heketi.json: EOF
Heketi 5.0.0

Version-Release number of selected component (if applicable):
cns-deploy-5.0.0-18.el7rhgs.x86_64

How reproducible:
Always. This issue is seen on two different steps and consistently seen

Steps to Reproduce:
1. Install cns using cns-deploy

Actual results:
cns-deployment fails

Expected results:
cns-deployment should pass

Additional info:

Comment 3 krishnaram Karthick 2017-08-18 16:16:42 UTC
Created attachment 1315288 [details]
cns-deploy logs

Comment 4 Mohamed Ashiq 2017-08-21 08:04:59 UTC
Can you mention the release tag for easy verification?

Comment 5 krishnaram Karthick 2017-08-21 09:26:51 UTC
(In reply to Mohamed Ashiq from comment #4)
> Can you mention the release tag for easy verification?

rhgs3/rhgs-volmanager-rhel7:3.3.0-10 is the heketi image, if you are looking for that information.

Comment 6 Michael Adam 2017-08-21 10:35:12 UTC
The rpm needs to package the new file heketi.json.template from the upstream

Comment 12 krishnaram Karthick 2017-09-01 12:55:28 UTC
cns-deploy completes to configure heketi and gluster pods in build - cns-deploy-5.0.0-23.el7rhgs.x86_64

Moving the bug to verified.

Comment 14 errata-xmlrpc 2017-10-11 07:12:11 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/RHEA-2017:2881

Comment 15 vinutha 2018-12-06 19:43:16 UTC
Marking qe-test-coverage as - since the preferred mode of deployment is using ansible


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