Bug 1229261
| Summary: | data tiering: do not allow tiering related volume set options on a regular volume | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Nag Pavan Chilakam <nchilaka> |
| Component: | tier | Assignee: | Mohammed Rafi KC <rkavunga> |
| Status: | CLOSED ERRATA | QA Contact: | Nag Pavan Chilakam <nchilaka> |
| Severity: | low | Docs Contact: | |
| Priority: | high | ||
| Version: | rhgs-3.1 | CC: | bugs, dlambrig, josferna, rcyriac, rhs-bugs, rkavunga, skoduri, storage-qa-internal, trao, vagarwal |
| Target Milestone: | --- | Keywords: | Triaged |
| Target Release: | RHGS 3.1.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | glusterfs-3.7.1-5 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1216960 | Environment: | |
| Last Closed: | 2015-07-29 04:59:08 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: | 1216960, 1230560 | ||
| Bug Blocks: | 1202842 | ||
|
Description
Nag Pavan Chilakam
2015-06-08 10:40:42 UTC
Downstream patch: https://code.engineering.redhat.com/gerrit/50617 moving back to modified, was moved to on_qa by errata tool. i could reproduce this problem: [root@rhsqa14-vm1 ~]# gluster v create pest replica 2 10.70.47.165:/rhs/brick1/p0 10.70.47.163:/rhs/brick1/p0 10.70.47.165:/rhs/brick2/p0 10.70.47.163:/rhs/brick2/p0 volume create: pest: success: please start the volume to access data [root@rhsqa14-vm1 ~]# gluster v start pest volume start: pest: success [root@rhsqa14-vm1 ~]# [root@rhsqa14-vm1 ~]# gluster v set pest cluster.tier-demote-frequency 10 volume set: success [root@rhsqa14-vm1 ~]# gluster v set pest cluster.tier-promote-frequency 10 volume set: success [root@rhsqa14-vm1 ~]# gluster v set pest features.ctr-enabled Usage: volume set <VOLNAME> <KEY> <VALUE> [root@rhsqa14-vm1 ~]# gluster v set pest features.ctr-enabled on volume set: success [root@rhsqa14-vm1 ~]# gluster v info pest Volume Name: pest Type: Distributed-Replicate Volume ID: a80f568b-0a9a-4d8e-bed0-b6fabe9fbdc8 Status: Started Number of Bricks: 2 x 2 = 4 Transport-type: tcp Bricks: Brick1: 10.70.47.165:/rhs/brick1/p0 Brick2: 10.70.47.163:/rhs/brick1/p0 Brick3: 10.70.47.165:/rhs/brick2/p0 Brick4: 10.70.47.163:/rhs/brick2/p0 Options Reconfigured: features.ctr-enabled: on cluster.tier-promote-frequency: 10 cluster.tier-demote-frequency: 10 performance.readdir-ahead: on [root@rhsqa14-vm1 ~]# [root@rhsqa14-vm1 ~]# rpm -qa | grep gluster gluster-nagios-addons-0.2.3-1.el6rhs.x86_64 glusterfs-fuse-3.7.1-4.el6rhs.x86_64 glusterfs-geo-replication-3.7.1-4.el6rhs.x86_64 gluster-nagios-common-0.2.0-1.el6rhs.noarch glusterfs-libs-3.7.1-4.el6rhs.x86_64 glusterfs-client-xlators-3.7.1-4.el6rhs.x86_64 glusterfs-api-3.7.1-4.el6rhs.x86_64 glusterfs-server-3.7.1-4.el6rhs.x86_64 glusterfs-rdma-3.7.1-4.el6rhs.x86_64 vdsm-gluster-4.16.20-1.1.el6rhs.noarch glusterfs-3.7.1-4.el6rhs.x86_64 glusterfs-cli-3.7.1-4.el6rhs.x86_64 [root@rhsqa14-vm1 ~]# why are you trying with build -3.7.1-4 while we have a new build -3.7.1-5 today. [root@rhsqa14-vm1 ~]# gluster v info good Volume Name: good Type: Distributed-Replicate Volume ID: 9425c6b8-a7e3-49df-a354-fa4d572507bc Status: Started Number of Bricks: 2 x 2 = 4 Transport-type: tcp Bricks: Brick1: 10.70.47.165:/rhs/brick1/g0 Brick2: 10.70.47.163:/rhs/brick1/g0 Brick3: 10.70.47.165:/rhs/brick2/g0 Brick4: 10.70.47.163:/rhs/brick2/g0 Options Reconfigured: performance.readdir-ahead: on [root@rhsqa14-vm1 ~]# gluster v set good cluster.tier-demote-frequency 10 volume set: failed: Volume good is not a tier volume. Option cluster.tier-demote-frequency is only valid for tier volume. [root@rhsqa14-vm1 ~]# gluster v set good cluster.tier-promote-frequency 10 volume set: failed: Volume good is not a tier volume. Option cluster.tier-promote-frequency is only valid for tier volume. [root@rhsqa14-vm1 ~]# gluster v set good features.ctr-enabled on volume set: success [root@rhsqa14-vm1 ~]# i see that feature.ctr-enabled can be applied on regular volume. please confirm about ctr value. I considered tiering related volume set commands as everything which starts with "cluster.tier". IMHO, ctr is implemented as a stand alone xlator, so restricting the ctr xlator only for tiering is not good. with above explanation regarding the ctr option this bug is verified. 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://rhn.redhat.com/errata/RHSA-2015-1495.html |