Hide Forgot
Created attachment 1266587 [details] cnsdeploy-log Description of problem: cns-deploy tool is broken in the build - cns-deploy-4.0.0-8.el7rhgs.x86_64 Please find the console output pasted below. [root@dhcp46-202 ~]# cns-deploy -n storage-project -g topology-sample.json --verbose -l /var/log/cns-deploy.log Welcome to the deployment tool for GlusterFS on Kubernetes and OpenShift. Before getting started, this script has some requirements of the execution environment and of the container platform that you should verify. The client machine that will run this script must have: * Administrative access to an existing Kubernetes or OpenShift cluster * Access to a python interpreter 'python' * Access to the heketi client 'heketi-cli' Each of the nodes that will host GlusterFS must also have appropriate firewall rules for the required GlusterFS ports: * 2222 - sshd (if running GlusterFS in a pod) * 24007 - GlusterFS Daemon * 24008 - GlusterFS Management * 49152 to 49251 - Each brick for every volume on the host requires its own port. For every new brick, one new port will be used starting at 49152. We recommend a default range of 49152-49251 on each host, though you can adjust this to fit your needs. In addition, for an OpenShift deployment you must: * Have 'cluster_admin' role on the administrative account doing the deployment * Add the 'default' and 'router' Service Accounts to the 'privileged' SCC * Have a router deployed that is configured to allow apps to access services running in the cluster Do you wish to proceed with deployment? [Y]es, [N]o? [Default: Y]: y Using OpenShift CLI. NAME STATUS AGE storage-project Active 24m Using namespace "storage-project". Checking that heketi pod is not running ... Checking status of pods matching 'glusterfs=heketi-pod': No resources found. Timed out waiting for pods matching 'glusterfs=heketi-pod'. 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" Marking 'dhcp46-165.lab.eng.blr.redhat.com' as a GlusterFS node. node "dhcp46-165.lab.eng.blr.redhat.com" labeled Marking 'dhcp47-21.lab.eng.blr.redhat.com' as a GlusterFS node. node "dhcp47-21.lab.eng.blr.redhat.com" labeled Marking 'dhcp47-51.lab.eng.blr.redhat.com' as a GlusterFS node. node "dhcp47-51.lab.eng.blr.redhat.com" labeled Deploying GlusterFS pods. daemonset "glusterfs" created Waiting for GlusterFS pods to start ... Checking status of pods matching 'glusterfs-node=pod': glusterfs-1zs3l 1/1 Running 0 3m glusterfs-4jjz5 1/1 Running 0 3m glusterfs-w812j 1/1 Running 0 3m OK Flag --value has been deprecated, Use -p, --param instead. Flag --value has been deprecated, Use -p, --param instead. service "deploy-heketi" created route "deploy-heketi" created deploymentconfig "deploy-heketi" created Waiting for deploy-heketi pod to start ... Checking status of pods matching 'glusterfs=heketi-pod': deploy-heketi-1-8gk48 1/1 Running 0 1m OK Determining heketi service URL ... OK Error: unknown command "load" for "heketi-cli" Run 'heketi-cli --help' for usage. heketi topology loaded. Usage: heketi-cli [flags] heketi-cli [command] Examples: $ export HEKETI_CLI_SERVER=http://localhost:8080 $ heketi-cli volume list Available Commands: cluster Heketi cluster management device Heketi device management node Heketi Node Management setup-openshift-heketi-storage Setup OpenShift/Kubernetes persistent storage for Heketi topology Heketi Topology Management volume Heketi Volume Management Flags: --json Print response as JSON --secret string Secret key for specified user. Can also be set using the environment variable HEKETI_CLI_KEY -s, --server string Heketi server. Can also be set using the environment variable HEKETI_CLI_SERVER --user string Heketi user. Can also be set using the environment variable HEKETI_CLI_USER -v, --version Print version Use "heketi-cli [command] --help" for more information about a command. heketi-storage.json file not found [root@dhcp46-202 ~]# oc get pods NAME READY STATUS RESTARTS AGE deploy-heketi-1-8gk48 1/1 Running 0 14m glusterfs-1zs3l 1/1 Running 0 17m glusterfs-4jjz5 1/1 Running 0 17m glusterfs-w812j 1/1 Running 0 17m storage-project-router-1-l68vj 1/1 Running 0 42m Version-Release number of selected component (if applicable): cns-deploy-4.0.0-8.el7rhgs.x86_64 heketi-client-4.0.0-4.el7rhgs.x86_64 How reproducible: 1/1 Steps to Reproduce: 1. configure oc cluster and run cns-deploy Actual results: cns-deploy fails after setting up depoy-heketi pod Expected results: cns-deploy should setup cns successfully Additional info:
Patch upstream merged: https://github.com/gluster/gluster-kubernetes/pull/213 RCA : # heketi-cli --user admin --secret "" topology load --json=topology-sample.json Is the right command. # heketi-cli --user admin --secret topology load --json=topology-sample.json Missing "" after secret causes topology as value for secret.
Verified the bug in build cns-deploy-4.0.0-9.el7rhgs.x86_64 The issue reported in this bug is not seen anymore.
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
Marking qe-test-coverage as - since the preferred mode of deployment is using ansible