Bug 1101937

Summary: wrong error message for mount points configuration
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Martin Kudlej <mkudlej>
Component: rhs-hadoopAssignee: Shubhendu Tripathi <shtripat>
Status: CLOSED ERRATA QA Contact: Ondřej Komárek <okomarek>
Severity: low Docs Contact:
Priority: low    
Version: rhgs-3.0CC: aavati, bchilds, eboyd, esammons, matt, nlevinki, okomarek, rhs-bugs, shtripat, vbellur
Target Milestone: Release CandidateKeywords: UpcomingRelease, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rhs-hadoop-2.3.3-2 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-11-24 11:54:33 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: 1159155    

Description Martin Kudlej 2014-05-28 08:17:39 UTC
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

Comment 3 Ondřej Komárek 2014-11-05 14:56:39 UTC
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.

Comment 5 errata-xmlrpc 2014-11-24 11:54:33 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://rhn.redhat.com/errata/RHEA-2014-1275.html