Description of problem: I haven't set up "fs.glusterfs.volumes" properly and I've seen in logs: Could not find mount point for volume: ... Which is confusing error message. I think it should be corrected. Version-Release number of selected component (if applicable): glusterfs-3.6.0.6-1.el6rhs.x86_64 glusterfs-api-3.6.0.6-1.el6rhs.x86_64 glusterfs-api-devel-3.6.0.6-1.el6rhs.x86_64 glusterfs-cli-3.6.0.6-1.el6rhs.x86_64 glusterfs-debuginfo-3.6.0.6-1.el6rhs.x86_64 glusterfs-devel-3.6.0.6-1.el6rhs.x86_64 glusterfs-fuse-3.6.0.6-1.el6rhs.x86_64 glusterfs-geo-replication-3.6.0.6-1.el6rhs.x86_64 glusterfs-libs-3.6.0.6-1.el6rhs.x86_64 glusterfs-rdma-3.6.0.6-1.el6rhs.x86_64 glusterfs-server-3.6.0.6-1.el6rhs.x86_64 python-rhsm-1.9.7-1.el6_5.x86_64 redhat-storage-logos-60.0.17-1.el6rhs.noarch rhs-hadoop-2.3.0-6.noarch rhs-hadoop-install-1_11-1.el6rhs.noarch How reproducible: 100% Steps to Reproduce: 1. do not configure plugin correctly and start all services 2. look into logs
Fixed here: https://github.com/shtripat/glusterfs-hadoop/commit/33cb8704d50dee5f36d92ba13e99075e8fb014dd
Tested with versions: glusterfs-3.6.0.30-1.el6rhs.x86_64 glusterfs-hadoop-distribution-glusterfs-hadoop-setup_hadoop-0.1-84.noarch glusterfs-rdma-3.6.0.30-1.el6rhs.x86_64 glusterfs-hadoop-distribution-glusterfs-hadoop-setup_gluster-0.2-54.noarch glusterfs-libs-3.6.0.30-1.el6rhs.x86_64 glusterfs-fuse-3.6.0.30-1.el6rhs.x86_64 glusterfs-server-3.6.0.30-1.el6rhs.x86_64 glusterfs-cli-3.6.0.30-1.el6rhs.x86_64 glusterfs-geo-replication-3.6.0.30-1.el6rhs.x86_64 glusterfs-hadoop-distribution-glusterfs-hadoop-setup_common-0.2-72.noarch glusterfs-api-3.6.0.30-1.el6rhs.x86_64 rhs-hadoop-install-2_28-1.el6rhs.noarch rhs-hadoop-2.3.3-3.el6rhs.noarch ambari-agent-1.6.1-98.x86_64 ambari-server-1.6.1-98.noarch Error message is now different: java.lang.RuntimeException: Invalid volume name: HadoopVol1, No mount point available for the volume. I find this error more appropriate -> 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://rhn.redhat.com/errata/RHEA-2014-1275.html