Bug 1743069 - bug-1482023-snpashot-issue-with-other-processes-accessing-mounted-path.t fails in brick mux regression spuriously
Summary: bug-1482023-snpashot-issue-with-other-processes-accessing-mounted-path.t fail...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: GlusterFS
Classification: Community
Component: tests
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-19 04:10 UTC by Atin Mukherjee
Modified: 2020-03-12 13:22 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-03-12 13:22:53 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gluster.org Gerrit 23262 0 None Open tests: mark bug-1482023-snpashot-issue-with-other-processes-accessing-mounted-path.t as BRICK_MUX_BAD_TEST 2019-08-19 06:14:51 UTC

Description Atin Mukherjee 2019-08-19 04:10:06 UTC 
Description of problem:

bug-1482023-snpashot-issue-with-other-processes-accessing-mounted-path.t fails in brick mux nightly run often. While we need to have a permanent fix to this with https://review.gluster.org/#/c/glusterfs/+/22949/ (which is WIP), this bug is to track this open defect.

Version-Release number of selected component (if applicable):
mainline

How reproducible:
Often
Comment 1 Worker Ant 2019-08-19 04:13:57 UTC 
REVIEW: https://review.gluster.org/23262 (tests: mark bug-1482023-snpashot-issue-with-other-processes-accessing-mounted-path.t as BRICK_MUX_BAD_TEST) posted (#1) for review on master by Atin Mukherjee
Comment 2 Worker Ant 2019-08-19 06:14:52 UTC 
REVIEW: https://review.gluster.org/23262 (tests: mark bug-1482023-snpashot-issue-with-other-processes-accessing-mounted-path.t as BRICK_MUX_BAD_TEST) merged (#1) on master by Atin Mukherjee
Comment 3 Worker Ant 2020-03-12 13:22:53 UTC 
This bug is moved to https://github.com/gluster/glusterfs/issues/1004, and will be tracked there from now on. Visit GitHub issues URL for further details
Note You need to log in before you can comment on or make changes to this bug.