[Bugs] [Bug 1647506] glusterd_brick_start wrongly discovers already-running brick

bugzilla at redhat.com bugzilla at redhat.com
Mon Nov 12 13:17:42 UTC 2018


--- Comment #7 from Mohit Agrawal <moagrawa at redhat.com> ---

Thanks for sharing the info. After analyzing the logs it is difficult to map
pid of running brick process. Usually, we got this type  of situation only in
the container environment while user do configure brick multiplex feature
(multiple bricks are attached with same brick)
but in this case you are getting an issue even without enabling brick

Would it be possible for you to test the patch if I do share the patch with you
or how can I share a test build(rpm) with you ??

Mohit Agrawal

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

More information about the Bugs mailing list