Descriptionkrishnaram Karthick
2017-09-04 11:36:21 UTC
Description of problem:
While setting up gluster-block via cns-deploy, following command fails.
/usr/bin/oc -n storage-project policy add-cluster-role-to-user glusterblock-provisioner-runner system:serviceaccount:storage-project:glusterblock-provisioner 2>&1
error: unknown command "add-cluster-role-to-user glusterblock-provisioner-runner system:serviceaccount:storage-project:glusterblock-provisioner"
snippet of cns-deploy:
----------------------
Ready to create and provide GlusterFS volumes.
/usr/bin/oc -n storage-project create -f /usr/share/heketi/templates/glusterblock-config.yaml
/usr/bin/oc -n storage-project create -f /usr/share/heketi/templates/glusterblock-config.yaml
clusterrole "glusterblock-provisioner-runner" created
serviceaccount "glusterblock-provisioner" created
/usr/bin/oc -n storage-project policy add-cluster-role-to-user glusterblock-provisioner-runner system:serviceaccount:storage-project:glusterblock-provisioner 2>&1
/usr/bin/oc -n storage-project policy add-cluster-role-to-user glusterblock-provisioner-runner system:serviceaccount:storage-project:glusterblock-provisioner 2>&1
error: unknown command "add-cluster-role-to-user glusterblock-provisioner-runner system:serviceaccount:storage-project:glusterblock-provisioner"
See 'oc policy -h' for help and examples.
/usr/bin/oc -n storage-project create -f /usr/share/heketi/templates/glusterblock-provisioner.yaml
/usr/bin/oc -n storage-project create -f /usr/share/heketi/templates/glusterblock-provisioner.yaml
deploymentconfig "glusterblock-provisioner" created
Waiting for glusterblock-provisioner pod to start ...
Checking status of pods matching '--selector=glusterfs=block-provisioner-pod':
p.s., complete set of cns-deploy log shall be attached.
Version-Release number of selected component (if applicable):
cns-deploy-5.0.0-29.el7rhgs.x86_64
How reproducible:
always
Steps to Reproduce:
1. setup gluster-block via cns-deploy
Comment 2krishnaram Karthick
2017-09-04 11:38:09 UTC
gluster-block cannot be setup via cns-deploy with this bug. Raising a blocker to get this bug fixed for cns 3.6
Comment 3krishnaram Karthick
2017-09-04 11:52:36 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