This bug was fixed in the package glusterfs - 3.4.2-1ubuntu1
---------------
glusterfs (3.4.2-1ubuntu1) trusty; urgency=low
* Merge from Debian unstable. Remaining changes:
- Updated mount blocking upstart job to wait until network is up for
all glusterfs mounts (LP: #1268064)
glusterfs (3.4.2-1) unstable; urgency=low
* New upstream release.
* Overwrite debian-watch-may-check-gpg-signature warning. There is no GPG
signature available.
-- Louis Zuckerman <[email protected]> Fri, 10 Jan 2014 21:40:13 -0500
** Changed in: glusterfs (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to glusterfs in Ubuntu.
https://bugs.launchpad.net/bugs/1268064
Title:
Remote glusterfs mounts fail during boot because network is not yet
available
Status in “glusterfs” package in Ubuntu:
Fix Released
Bug description:
I'm the upstream package maintainer & I'm filing this bug along with a
patch (merge request) for the upcoming trusty release.
Affects: Ubuntu trusty (14.04)
Problem: Upstart tries the glusterfs mounts before the network is
available during boot, and they fail.
Solution: An upstart task to block glusterfs mounts during boot until
the network is ready
Patch:
The glusterfs 3.4.1 package currently in trusty has outdated upstart
jobs. The patch I will be submitting shortly makes two changes: move
the mounting-glusterfs blocker job from glusterfs-server to glusterfs-
client; change the wait-for-state condition from glusterfs-server to
static-network-up.
Background:
When I wrote the old mount blocker, back in early 2012, remote mounts
worked fine but localhost glusterfs mounts failed because the local
glusterfs-server daemon had not started by the time the mounts were
executed. At some point since then we found that remote mounts would
also fail during boot, perhaps by better testing or maybe a change in
ubuntu since precise, I'm not sure. The new mount blocker job
resolves both problems as far as I know. I provide the official
glusterfs packages for ubuntu in PPAs
(https://launchpad.net/~semiosis/+archive/ubuntu-glusterfs-3.4 for
example) and many people use those packages and have tested the new
mount blocker.
Log file showing the mount fail with the current 3.4.1 package...
[2014-01-11 03:27:38.480966] I [glusterfsd.c:1910:main]
0-/usr/sbin/glusterfs: Started running /usr/sbin/glusterfs version 3.4.1
(/usr/sbin/glusterfs --volfile-id=foo --volfile-server=192.168.192.104 /mnt/foo)
[2014-01-11 03:27:38.489565] I [socket.c:3480:socket_init] 0-glusterfs: SSL
support is NOT enabled
[2014-01-11 03:27:38.489610] I [socket.c:3495:socket_init] 0-glusterfs: using
system polling thread
[2014-01-11 03:27:38.489691] E [common-utils.c:211:gf_resolve_ip6]
0-resolver: getaddrinfo failed (Name or service not known)
[2014-01-11 03:27:38.489705] E
[name.c:249:af_inet_client_get_remote_sockaddr] 0-glusterfs: DNS resolution
failed on host 192.168.192.104
[2014-01-11 03:27:38.489747] E [glusterfsd-mgmt.c:1870:mgmt_rpc_notify]
0-glusterfsd-mgmt: failed to connect with remote-host: Success
[2014-01-11 03:27:38.489759] I [glusterfsd-mgmt.c:1873:mgmt_rpc_notify]
0-glusterfsd-mgmt: -1 connect attempts left
[2014-01-11 03:27:38.490749] W [glusterfsd.c:1002:cleanup_and_exit]
(-->/usr/sbin/glusterfs(glusterfs_mgmt_init+0x15d) [0x7f7127d2d89d]
(-->/usr/lib/x86_64-linux-gnu/libgfrpc.so.0(rpc_clnt_start+0x12)
[0x7f7127675342] (-->/usr/sbin/glusterfs(+0xd1fa) [0x7f7127d2e1fa]))) 0-:
received signum (1), shutting down
[2014-01-11 03:27:38.490776] I [fuse-bridge.c:5260:fini] 0-fuse: Unmounting
'/mnt/foo'.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/1268064/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~ubuntu-ha
Post to : [email protected]
Unsubscribe : https://launchpad.net/~ubuntu-ha
More help : https://help.launchpad.net/ListHelp
