Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1238052

Summary: Quota list is not working on tiered volume.
Product: [Community] GlusterFS Reporter: Mohammed Rafi KC <rkavunga>
Component: tieringAssignee: bugs <bugs>
Status: CLOSED CURRENTRELEASE QA Contact: bugs <bugs>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 3.7.2CC: bugs, josferna, rkavunga, trao, vagarwal
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: Tiering
Fixed In Version: glusterfs-3.7.3 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1236128 Environment:
Last Closed: 2015-07-30 09:51:57 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: 1230540, 1236128, 1254439    
Bug Blocks: 1229259, 1260923    

Comment 1 Anand Avati 2015-07-01 05:49:10 UTC
REVIEW: http://review.gluster.org/11475 (tiering/quota: failed to match subvolume) posted (#1) for review on release-3.7 by mohammed rafi  kc (rkavunga)

Comment 2 Anand Avati 2015-07-01 15:02:32 UTC
COMMIT: http://review.gluster.org/11475 committed in release-3.7 by Dan Lambright (dlambrig) 
------
commit 8e4cc51e36514db9bf1ca2beac993091c95c649a
Author: Mohammed Rafi KC <rkavunga>
Date:   Tue Jun 30 11:15:54 2015 +0530

    tiering/quota: failed to match subvolume
    
    quota daemon choose subvolume for a volume using
    volume-id specified in graph. For that it expect
    a subvolume (DHT) to be named as volume-id. But
    tiering translator comes above dht, so it failed to
    match the correct subvolume.
    
    >Change-Id: I63d4b63cd8fb2806bc7b2b2f100dbef62202e6da
    >BUG: 1236128
    >Signed-off-by: Mohammed Rafi KC <rkavunga>
    >Reviewed-on: http://review.gluster.org/11431
    >Reviewed-by: Joseph Fernandes
    >Tested-by: NetBSD Build System <jenkins.org>
    >Tested-by: Gluster Build System <jenkins.com>
    >Reviewed-by: Dan Lambright <dlambrig>
    >Tested-by: Dan Lambright <dlambrig>
    
    (cherry picked from commit e9807b8e5799cd5f62fcaa1f228bb470f4bc1157)
    
    Change-Id: I2a2230e3f9172c08cef993854a3a8ac6eb7271c4
    BUG: 1238052
    Signed-off-by: Mohammed Rafi KC <rkavunga>
    Reviewed-on: http://review.gluster.org/11475
    Tested-by: NetBSD Build System <jenkins.org>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Dan Lambright <dlambrig>
    Tested-by: Dan Lambright <dlambrig>

Comment 3 Kaushal 2015-07-30 09:51:57 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.3, please open a new bug report.

glusterfs-3.7.3 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/12078
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user