Bug 1351767

Summary: Receiving VolumeDriver.Mount error when using glusterfs plugin with Docker v1.10, MongoDB v3.2.6
Product: [Community] GlusterFS Reporter: chris.mitchell
Component: coreAssignee: bugs <bugs>
Status: CLOSED EOL QA Contact:
Severity: medium Docs Contact:
Priority: low    
Version: 3.7.8CC: amukherj, bugs, chris.mitchell
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-03-08 11:03:12 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:
Attachments:
Description Flags
glusterfs log none

Description chris.mitchell 2016-06-30 18:50:19 UTC 
Description of problem:
Docker container fails to start and reports back VolumeDriver.Mount error

Version-Release number of selected component (if applicable):
Docker v1.10
MongoDB v3.2

How reproducible:
Every time.

Steps to Reproduce:
1. Install latest version of Docker
2. Pull MongoDB v3.2.6 from Docker public repo
3. docker run --volume-driver=glusterfs --volume=mongo:/data/db mongo_docker_image

Actual results:
Container starts up and fails

Expected results:
Container to run using glusterfs plugin

Additional info:
Works fine when rolling back to MongoDB v2.6. This issue could be related to the storage engine changes in v3.
Comment 1 Atin Mukherjee 2016-07-03 09:52:21 UTC 
Please attach all the glusterfs related logs.
Comment 2 chris.mitchell 2016-07-13 14:50:55 UTC 
Created attachment 1179312 [details]
glusterfs log
Comment 3 chris.mitchell 2016-08-04 12:53:03 UTC 
Hello, just checking in to see if there have been any updates or any additional info needed. Thank you.
Comment 4 Atin Mukherjee 2017-01-25 08:03:57 UTC 
(In reply to chris.mitchell from comment #2)
> Created attachment 1179312 [details]
> glusterfs log

I see only the mount log attached here. You'd need to provide all the client, brick and glusterd log files to help us in analysing the issue.
Comment 5 Kaushal 2017-03-08 11:03:12 UTC 
This bug is getting closed because GlusteFS-3.7 has reached its end-of-life.

Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS.
If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release.
Comment 6 Red Hat Bugzilla 2023-09-14 03:27:33 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days