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:
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
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.
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?
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
The actual fix/workaround for now is to reintroduce the parameter to the Template and then change: value: 15 to: value: "15" with quotes.
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.
gluster-block setup works in build - cns-deploy-5.0.0-32.el7rhgs moving the bug to verified.
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