Bug 770506 - glusterd doesn't wait for network to start
Summary: glusterd doesn't wait for network to start
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: glusterfs
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
Assignee: Kaleb KEITHLEY
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-27 07:08 UTC by Renich Bon Ciric
Modified: 2013-02-13 15:55 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 15:55:23 UTC
Type: ---


Attachments (Terms of Use)

Description Renich Bon Ciric 2011-12-27 07:08:19 UTC
Description of problem:
The glusterd daemon is not waiting for network to be ready. This causes it to stop.

Version-Release number of selected component (if applicable):
glusterfs-3.2.5-3.fc16.x86_64

How reproducible:
just install gluster, chkconfig glusterd on (not systemd yet) and chkconfig network on

Actual results:
It's trying to start even when the network is not ready.

Expected results:
It should wait for the network.

Additional info:
IMHO, priority is set correctly but systemd is not taking this into account. There should be a work around if you do a 5 second sleep in the /etc/rc.d/init.d/glusterd

Comment 1 Renich Bon Ciric 2011-12-29 21:06:12 UTC
Ok, this was solved by appending "network" to "required" in /etc/init.d/glusterd

Comment 2 Carl Byington 2012-04-14 23:56:06 UTC
It seems to still fail with

glusterfs-3.2.6-1.fc16.x86_64
glusterfs-server-3.2.6-1.fc16.x86_64
glusterfs-fuse-3.2.6-1.fc16.x86_64

I just rebooted one of the cluster machines, and 

gluster peer status
Connection failed. Please check if gluster daemon is operational.

systemctl restart glusterd.service
that worked to bring the machine back into the cluster.

Comment 3 Fedora End Of Life 2013-01-16 15:11:18 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Fedora Admin XMLRPC Client 2013-01-18 15:11:32 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 5 Fedora End Of Life 2013-02-13 15:55:26 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.