[Bugs] [Bug 1503173] New: [Geo-rep] Master and slave mounts are not accessible to take client profile info

[bugzilla at redhat.com]

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

            Bug ID: 1503173
           Summary: [Geo-rep] Master and slave mounts are not accessible
                    to take client profile info
           Product: Red Hat Gluster Storage
           Version: 3.3
         Component: geo-replication
          Severity: medium
          Assignee: avishwan at redhat.com
          Reporter: khiremat at redhat.com
        QA Contact: rhinduja at redhat.com
                CC: bugs at gluster.org, csaba at redhat.com,
                    rhs-bugs at redhat.com, storage-qa-internal at redhat.com
        Depends On: 1433506
            Blocks: 1438330



+++ This bug was initially created as a clone of Bug #1433506 +++

Description of problem:
Master and slave geo-rep auxiliary mounts are not accessible to user to take
client profile info or do any other client stack analysis. The mounts are lazy
unmounted after changing the current directory to the respective mount point.
So that only geo-rep worker has access to it.

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


How reproducible:
Always

Steps to Reproduce:
1. Setup geo-rep session between master and slave volume
2. Try to take the client side profile info of either master volume or slave
volume


Actual results:
Not able to take client profile info of active geo-rep master and slave mount
points on which I/O is happening

Expected results:
When needed, it should be possible to take client profile info of active
geo-rep master and slave mount points on which I/O is happening


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1433506
[Bug 1433506] [Geo-rep] Master and slave mounts are not accessible to take
client profile info
https://bugzilla.redhat.com/show_bug.cgi?id=1438330
[Bug 1438330] [Geo-rep] Master and slave mounts are not accessible to take
client profile info
-- 
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=nXXomY6byX&a=cc_unsubscribe