[Bugs] [Bug 1599628] New: To find a compatible brick ignore diagnostics.brick-log-level option while brick mux is enabled

[bugzilla at redhat.com]

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

            Bug ID: 1599628
           Summary: To find a compatible brick ignore
                    diagnostics.brick-log-level option while brick mux is
                    enabled
           Product: GlusterFS
           Version: mainline
         Component: glusterd
          Assignee: bugs at gluster.org
          Reporter: moagrawa at redhat.com
                CC: bugs at gluster.org



Description of problem:
To find a compatible brick ignore diagnostics.brick-log-level option while
brick mux is enabled.
Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.setup 2 volumes and enable brick mux
2.Enable diagnostics.brick-log-level DEBUG for anyone volume
3. Start both volumes

Actual results:
Both volumes are getting separate brick process because glusted compares
brick option at the time of attaching a brick with already running brick.If
it founds any difference then it starts a brick as a separate process.

Expected results:
Both volumes should get same pid because there is no impact on functionality
after enabling DEBUG for log-level for any volume.

Additional info:

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