Bug 1083882

Summary: [SNAPSHOT]: snapshot config <vol> is to list the config, it should not acquire the volume lock to list.
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Rahul Hinduja <rhinduja>
Component: snapshotAssignee: Sachin Pandit <spandit>
Status: CLOSED ERRATA QA Contact: Rahul Hinduja <rhinduja>
Severity: low Docs Contact:
Priority: low    
Version: rhgs-3.0CC: nsathyan, rhs-bugs, spandit, ssamanta, storage-qa-internal, vagarwal
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: SNAPSHOT
Fixed In Version: glusterfs-3.6.0-3.0.el6rhs Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1087677 (view as bug list) Environment:
Last Closed: 2014-09-22 19:33:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1087677    

Description Rahul Hinduja 2014-04-03 07:33:28 UTC 
Description of problem:
=======================

In a scenario where a snap creation is in progress and a user tries to list the config of that particular volume, it fails with "Another transition is in progress". The listing of volume configuration should not acquire a lock and it should be successful. Also, listing the complete system config information using "gluster snapshot config" works.

This could be the reason as we have single command to list and set
"snapshot config [volname] [snap-max-hard-limit <count>] [snap-max-soft-limit <percent>] - Snapshot Config."

But for a user the listing should not acquire a lock.

[root@snapshot-12 ~]# gluster snapshot config vol0
Snapshot Config : failed: Another transaction is in progress. Please try again after sometime.
Snapshot command failed
[root@snapshot-12 ~]# 



Version-Release number of selected component (if applicable):
==============================================================
glusterfs-3.4.1.7.snap.mar27.2014git-1.el6.x86_64


How reproducible:
=================
1/1


Steps to Reproduce:
===================
1. Start creating snapshot 
2. While snapshot creation is inprogress list the config using "gluster snapshot config <vol-name>"


Actual results:
===============

[root@snapshot-12 ~]# gluster snapshot config vol0
Snapshot Config : failed: Another transaction is in progress. Please try again after sometime.
Snapshot command failed
[root@snapshot-12 ~]# 

Expected results:
=================

[root@snapshot-12 ~]# gluster snapshot config vol0

Snapshot System Configuration:
snap-max-hard-limit : 70
snap-max-soft-limit : 90%

Snapshot Volume Configuration:

Volume : vol0
snap-max-hard-limit : 256
Effective snap-max-hard-limit : 70
Effective snap-max-soft-limit : 63 (90%)
[root@snapshot-12 ~]#
Comment 3 Nagaprasad Sathyanarayana 2014-04-21 06:18:22 UTC 
Marking snapshot BZs to RHS 3.0.
Comment 4 Sachin Pandit 2014-05-06 07:22:37 UTC 
The Patch which fixes this bug can be found in http://review.gluster.org/#/c/7458/
Comment 5 Rahul Hinduja 2014-05-15 12:25:12 UTC 
verified with build: glusterfs-3.6.0.1-1.el6rhs.x86_64

While the snapshot creation is in progress, able to list the config of a volume

[root@snapshot09 ~]# for i in {1..10} ; do time gluster snapshot create snap$i vol0 ; done 
snapshot create: success: Snap snap1 created successfully

real	0m10.914s
user	0m0.135s
sys	0m0.030s



 

[root@snapshot10 ~]# gluster snapshot config vol0

Snapshot System Configuration:
snap-max-hard-limit : 200
snap-max-soft-limit : 90%

Snapshot Volume Configuration:

Volume : vol0
snap-max-hard-limit : 256
Effective snap-max-hard-limit : 200
Effective snap-max-soft-limit : 180 (90%)
[root@snapshot10 ~]# 


Moving the bug to verified
Comment 6 Nagaprasad Sathyanarayana 2014-05-19 10:56:50 UTC 
Setting flags required to add BZs to RHS 3.0 Errata
Comment 8 errata-xmlrpc 2014-09-22 19:33:42 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.

http://rhn.redhat.com/errata/RHEA-2014-1278.html