Bug 1487987

Summary: cns-deployment fails
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: krishnaram Karthick <kramdoss>
Component: cns-deploy-toolAssignee: Michael Adam <madam>
Status: CLOSED ERRATA QA Contact: krishnaram Karthick <kramdoss>
Severity: high Docs Contact:
Priority: unspecified    
Version: cns-3.6CC: hchiramm, jarrpa, rcyriac, rhs-bugs, rtalur, vinug
Target Milestone: ---Keywords: Regression, TestBlocker
Target Release: CNS 3.6   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: cns-deploy-5.0.0-31.el7rhgs Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-10-11 07:12:11 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: 1445448    

Description krishnaram Karthick 2017-09-04 04:33:12 UTC
Description of problem:
cns-deployment fails as the glusterfs template doesn't get created.

oc create -f /usr/share/heketi/templates/glusterfs-template.yaml 
Error from server (BadRequest): error when creating "/usr/share/heketi/templates/glusterfs-template.yaml": Template in version "v1" cannot be handled as a Template: [pos 3216]: json: expect char '"' but got char '1'


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

How reproducible:
always

Steps to Reproduce:
1. Try to deploy cns using cns-deploy tool

Actual results:
cns-deploy fails

Expected results:
cns-deploy should succeed

Additional info:

Comment 3 krishnaram Karthick 2017-09-04 04:45:49 UTC
diff between the previous template (cns-deploy-5.0.0-25.el7rhgs.x86_64) and new template 

[root@dhcp46-68 ~]# diff glusterfs-template.yaml /usr/share/heketi/templates/glusterfs-template.yaml 
36c36
<         - image: rhgs3/rhgs-server-rhel7:3.3.0-18
---
>         - image: rhgs3/rhgs-server-rhel7:3.3.0-15
39,45d38
<           resources:
<             requests:
<               memory: 100Mi
<               cpu: 100m
<           env:
<           - name: GB_GLFS_LRU_COUNT
<             value: "${GB_GLFS_LRU_COUNT}"
47c40
<           - name: glusterfs-block
---
>           - name: glusterfs-gblock
98a92
>           resources: {}
101c95
<         - name: glusterfs-block
---
>         - name: glusterfs-gblock
142,146d135
< - name: GB_GLFS_LRU_COUNT
<   displayName: Maximum number of block hosting volumes
<   description: This value is to set maximum number of block hosting volumes.
<   value: 15
<   required: true

Comment 4 krishnaram Karthick 2017-09-04 06:18:19 UTC
The issue seems to be in this part of the template

< - name: GB_GLFS_LRU_COUNT
<   displayName: Maximum number of block hosting volumes
<   description: This value is to set maximum number of block hosting volumes.
<   value: 15
<   required: true

Removing this part allows template to be created.

Comment 5 krishnaram Karthick 2017-09-04 06:27:16 UTC
so as a workaround this is what I'm planning to do, 

update this part of the template 

from,

<           env:
<           - name: GB_GLFS_LRU_COUNT
<             value: "${GB_GLFS_LRU_COUNT}"

with,

<           env:
<           - name: GB_GLFS_LRU_COUNT
<             value: 15

And remove the below part.

< - name: GB_GLFS_LRU_COUNT
<   displayName: Maximum number of block hosting volumes
<   description: This value is to set maximum number of block hosting volumes.
<   value: 15
<   required: true

Can dev confirm if this workaround can be used until we have a build with a fix?

Comment 6 krishnaram Karthick 2017-09-04 06:37:37 UTC
Tried cns-deploy after making changes. gluster pod seems to be crashing.

[root@dhcp46-207 ~]# oc logs glusterfs-d4q9b
You need to set GB_GLFS_LRU_COUNT, TCMU_LOG_DIR env variable

Comment 7 Jose A. Rivera 2017-09-05 01:27:54 UTC
The actual fix/workaround for now is to reintroduce the parameter to the Template and then change:

   value: 15

to:

   value: "15"

with quotes.

Comment 11 krishnaram Karthick 2017-09-06 09:23:10 UTC
with Build cns-deploy-5.0.0-30.el7rhgs, gluster pod crashes while cns-deploy is run 'You need to set GB_GLFS_LRU_COUNT, TCMU_LOG_DIR env variable'

The template has two 'env' set.

          env:
          - name: GB_GLFS_LRU_COUNT
            value: "${GB_GLFS_LRU_COUNT}"
          - name: TCMU_LOG_DIR
            value: "${TCMU_LOG_DIR}"

.
.
.
.

          env:
          - name: GB_LOGDIR
            value: "/var/log/glusterfs/gluster-block/"


cns-deploy worked when these two env were merged. Moving the bug back to assigned to make this change in the glusterfs-template.

Comment 12 krishnaram Karthick 2017-09-07 08:56:12 UTC
gluster-block setup works in build - cns-deploy-5.0.0-32.el7rhgs

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