[Bugs] [Bug 1707658] New: AMQ pod cannot mount a gluster volume - failed to fetch volume file

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1707658

            Bug ID: 1707658
           Summary: AMQ pod cannot mount a gluster volume - failed to
                    fetch volume file
           Product: GlusterFS
           Version: mainline
                OS: Linux
            Status: NEW
         Component: core
          Severity: medium
          Priority: medium
          Assignee: bugs at gluster.org
          Reporter: srakonde at redhat.com
                CC: amukherj at redhat.com, atumball at redhat.com,
                    bmekala at redhat.com, nchilaka at redhat.com,
                    nravinas at redhat.com, rhs-bugs at redhat.com,
                    sankarshan at redhat.com, srakonde at redhat.com,
                    vbellur at redhat.com
        Depends On: 1705888
  Target Milestone: ---
             Group: private
    Classification: Community



Description of problem:

Gluster version installed on the nodes:

glusterfs-libs-3.12.2-47.el7rhgs.x86_64
glusterfs-3.12.2-47.el7rhgs.x86_64
glusterfs-client-xlators-3.12.2-47.el7rhgs.x86_64
glusterfs-server-3.12.2-47.el7rhgs.x86_64
glusterfs-api-3.12.2-47.el7rhgs.x86_64
glusterfs-cli-3.12.2-47.el7rhgs.x86_64
glusterfs-fuse-3.12.2-47.el7rhgs.x86_64
python2-gluster-3.12.2-47.el7rhgs.x86_64
glusterfs-geo-replication-3.12.2-47.el7rhgs.x86_64
gluster-block-0.2.1-31.el7rhgs.x86_64

AMQ pod " "broker-amq-1_gp-amq-cluster" cannot start properly because it cannot
mount volume vol_c03b4bf4a04adb7ce011d597d1f95706

>From the pod logs:

Warning Failed Mount    MountVolume.SetUp failed for volume
"pvc-be25d142-545f-11e9-a0f4-566f86f30040" : mount failed: 
mount failed: exit status 1 
Mounting command: systemd-run Mounting arguments: --description=Kubernetes
transient mount for
/var/lib/origin/openshift.local.volumes/pods/723b7932-6a7b-11e9-aed6-566f86f30041/volumes/kubernetes.io~glusterfs/pvc-be25d142-545f-11e9-a0f4-566f86f30040
--scope -- mount -t glusterfs -o
log-level=ERROR,log-file=/var/lib/origin/openshift.local.volumes/plugins/kubernetes.io/glusterfs/pvc-be25d142-545f-11e9-a0f4-566f86f30040/broker-amq-1-glusterfs.log,backup-volfile-servers=<server
ip's>,auto_unmount ip:vol_c03b4bf4a04adb7ce011d597d1f95706
/var/lib/origin/openshift.local.volumes/pods/723b7932-6a7b-11e9-aed6-566f86f30041/volumes/kubernetes.io~glusterfs/pvc-be25d142-545f-11e9-a0f4-566f86f30040
Output: Running scope as unit run-69719.scope. Mount failed. Please check the
log file for more details. 

The following error information was pulled from the glusterfs log to help
diagnose this issue: 

[2019-04-29 12:36:02.371455] E [glusterfsd-mgmt.c:2073:mgmt_getspec_cbk]
0-mgmt: failed to fetch volume file (key:vol_c03b4bf4a04adb7ce011d597d1f95706) 
[2019-04-29 12:36:34.568768] E [glusterfsd-mgmt.c:2073:mgmt_getspec_cbk]
0-mgmt: failed to fetch volume file (key:vol_c03b4bf4a04adb7ce011d597d1f95706)

So the client cannot access the associated volume file for this volume.

-- 
You are receiving this mail because:
You are the assignee for the bug.