[Bugs] [Bug 1569399] glusterfsd should be able to start without any other arguments than a single volfile.

bugzilla at redhat.com bugzilla at redhat.com
Tue May 8 21:16:51 UTC 2018


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

Worker Ant <bugzilla-bot at gluster.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|POST                        |MODIFIED



--- Comment #2 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/19893 committed in master by "Jeff Darcy"
<jeff at pl.atyp.us> with a commit message- protocol/server: don't assume there
would be a volfile id

Earlier glusterfs never had an assumption someone would start it with
right arguments, and brick processes would be spawned by a management
layer. It just assume the role based on the volfile. Other than
volfile, no other arguments should be technically mandatory for
working of glusterfs. With this patch, that assumption holds true.

Updates: github issue # 352

A note on why this particular issue for this basic sanity?

As per the design of thin-arbiter/tie-breaker, it can be started
independently on any machine, without need of glusterd. So, similar
to 'glusterd', we should be able to spawn a process with any translator
without options/volume id etc.

fixes: bz#1569399
Change-Id: I5c0650fe0bfde35ad94ccba60e63f6cdcd1ae5ff
Signed-off-by: Amar Tumballi <amarts at redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=YVSEovh1k1&a=cc_unsubscribe


More information about the Bugs mailing list