Bug 1106404

Summary: [SNAPSHOT]: glusterd log prints "invalid snap command" warning for every successful snapshot status
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Rahul Hinduja <rhinduja>
Component: snapshotAssignee: Avra Sengupta <asengupt>
Status: CLOSED CURRENTRELEASE QA Contact: Rahul Hinduja <rhinduja>
Severity: low Docs Contact:
Priority: unspecified    
Version: rhgs-3.0CC: rhs-bugs, storage-qa-internal
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: SNAPSHOT
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1106406 (view as bug list) Environment:
Last Closed: 2016-01-29 14:04:45 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: 1106406    

Description Rahul Hinduja 2014-06-09 09:30:26 UTC 
Description of problem:
=======================

Whenever snapshot command is successful against snapname or volumename, the glusterd logs prints a warning message as "invalid snap command" on all the nodes in cluster.

For example:
============

[root@rhs-arch-srv2 ~]# gluster snapshot status a40 | grep "Snap Name"
Snap Name : a40
[root@rhs-arch-srv2 ~]# 

glusterd logs:
==============

[2014-06-09 09:27:56.478558] W [glusterd-snapshot.c:6489:glusterd_snapshot_postvalidate] 0-management: invalid snap command



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


glusterfs-3.6.0.14-1.el6rhs.x86_64

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


Steps to Reproduce:
===================
1. Create and start a volume
2. Create a snapshot of a volume
3. Check the status of snapshot using
"gluster snapshot status <snap-name> | volume <vol-name>"
4. Check the glusterd logs

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

[2014-06-09 09:27:56.478558] W [glusterd-snapshot.c:6489:glusterd_snapshot_postvalidate] 0-management: invalid snap command


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

Warning should not be logged for successful and valid snap command.
Comment 1 Sachin Pandit 2014-06-09 09:34:43 UTC 
The patch which fixes this problem has been posted upstream.
http://review.gluster.org/#/c/8014/
Comment 3 Sachin Pandit 2014-06-23 05:20:17 UTC 
http://review.gluster.org/#/c/8014/ is merged upstream.
However as this bug does not have any blocker flag, I am
not going to send the patch downstream until Denali release.
Comment 5 Avra Sengupta 2016-01-29 14:04:45 UTC 
Won't be sending a fix to 3.0. The fix is available in 3.1