Bug 1472190 - [SAMBA-VSS]Previous version restore link is not visible over windows mount even after taking a snapshot
Summary: [SAMBA-VSS]Previous version restore link is not visible over windows mount ev...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: samba
Version: rhgs-3.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: RHGS 3.2.0 Async
Assignee: Anoop C S
QA Contact: Vivek Das
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-18 08:57 UTC by Vivek Das
Modified: 2017-08-01 07:46 UTC (History)
5 users (show)

Fixed In Version: glusterfs-3.8.4-18.6
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 07:46:44 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2339 0 normal SHIPPED_LIVE glusterfs bug fix update 2017-08-01 11:45:56 UTC

Description Vivek Das 2017-07-18 08:57:37 UTC
Description of problem:
With all the VSS plugins take a snapshot and activate it. Change data over windows mount and do a right click to check previous version, but no link is available.

Version-Release number of selected component (if applicable):
RHEL7.4
samba-4.6.3-4.el7rhgs.x86_64
glusterfs-server-3.8.4-18.5.el7rhgs.x86_64

How reproducible:
Always

Steps to Reproduce:
1.Enable USS
2.Enable VSS plugins
3.Take a snapshot and activate it
4.Over the windows mount change data
5.Right click and check for the restore the link

Actual results:
Restore link is not seen

Expected results:
Restore link should be available

Additional info:

Comment 4 Atin Mukherjee 2017-07-19 09:48:36 UTC
downstream patch : https://code.engineering.redhat.com/gerrit/#/c/112758/

Comment 6 Vivek Das 2017-07-24 05:38:34 UTC
With the latest version glusterfs-3.8.4-18.6 i am able to restore data in windows mount post taking a snapshot.
Marking this as verified.

Comment 8 errata-xmlrpc 2017-08-01 07:46:44 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2339


Note You need to log in before you can comment on or make changes to this bug.