Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1177911 - [USS]:Giving the wrong input while setting USS fails as expected but gluster v info shows the wrong value set in features.uss
[USS]:Giving the wrong input while setting USS fails as expected but gluster ...
Status: CLOSED ERRATA
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: snapshot (Show other bugs)
3.0
Unspecified Unspecified
high Severity high
: ---
: RHGS 3.1.0
Assigned To: Mohammed Rafi KC
storage-qa-internal@redhat.com
USS
:
Depends On:
Blocks: 1179175 1202842 1223636
  Show dependency treegraph
 
Reported: 2014-12-31 04:44 EST by senaik
Modified: 2016-09-17 09:04 EDT (History)
6 users (show)

See Also:
Fixed In Version: glusterfs-3.7.0-3.el6rhs
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-07-29 00:37:33 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:1495 normal SHIPPED_LIVE Important: Red Hat Gluster Storage 3.1 update 2015-07-29 04:26:26 EDT

  None (edit)
Description senaik 2014-12-31 04:44:09 EST
Description of problem:
========================
While setting USS on the volume if a wrong value is given, it fails as expected but features.uss shows the wrong value in gluster v info 


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

How reproducible:
================
always 


Steps to Reproduce:
=====================

gluster volume set vol0 features.uss jlkjlkjklj
volume set: failed: Commit failed on localhost. Please check the log file for more details.


[root@snapshot13 vol0]# gluster v i vol0
 
Volume Name: vol0
Type: Distributed-Replicate
Volume ID: 61cca20d-d92a-455d-a689-8670a37dd1b7
Status: Started
Snap Volume: no
Number of Bricks: 2 x 2 = 4
Transport-type: tcp
Bricks:
Brick1: snapshot13.lab.eng.blr.redhat.com:/rhs/brick1/b1
Brick2: snapshot14.lab.eng.blr.redhat.com:/rhs/brick1/b1
Brick3: snapshot15.lab.eng.blr.redhat.com:/rhs/brick1/b1
Brick4: snapshot16.lab.eng.blr.redhat.com:/rhs/brick1/b1
Options Reconfigured:
cluster.data-self-heal: on
features.uss: jlkjlkjklj
performance.readdir-ahead: on
auto-delete: disable
snap-max-soft-limit: 90
snap-max-hard-limit: 256


Actual results:
===============
The wrong value is shown in features.uss in gluster v info output 


Expected results:
=================
The wrong value should not be shown in gluster v info output. It should only show Enable/Disable 



Additional info:
Comment 2 Mohammed Rafi KC 2015-04-01 01:12:49 EDT
upstream bug : https://bugzilla.redhat.com/show_bug.cgi?id=1179175

upstream patch : http://review.gluster.org/#/c/9395/
Comment 6 senaik 2015-06-10 06:03:09 EDT
Version : glusterfs 3.7.1 built on Jun  9 2015 

Giving the wrong input while setting USS fails as below : 

gluster v set vol0 features.uss jsfjdsjf
volume set: failed: jsfjdsjf is not a valid boolean value. features.uss expects a valid boolean value.

Marking the bug as 'Verified'
Comment 7 senaik 2015-06-10 06:06:52 EDT
Adding to Comment 6 : 

gluster v info does not show the wrong value given: 

[root@inception ~]# gluster v info vol0
 
Volume Name: vol0
Type: Distributed-Replicate
Volume ID: 59aa030c-5009-4749-bb83-4963755cd3a6
Status: Started
Number of Bricks: 6 x 3 = 18
Transport-type: tcp
Bricks:
Brick1: inception.lab.eng.blr.redhat.com:/rhs/brick1/b1
Brick2: rhs-arch-srv2.lab.eng.blr.redhat.com:/rhs/brick1/b1
Brick3: rhs-arch-srv3.lab.eng.blr.redhat.com:/rhs/brick1/b1
Brick4: rhs-arch-srv4.lab.eng.blr.redhat.com:/rhs/brick1/b1
Brick5: inception.lab.eng.blr.redhat.com:/rhs/brick2/b2
Brick6: rhs-arch-srv2.lab.eng.blr.redhat.com:/rhs/brick2/b2
Brick7: rhs-arch-srv3.lab.eng.blr.redhat.com:/rhs/brick2/b2
Brick8: rhs-arch-srv4.lab.eng.blr.redhat.com:/rhs/brick2/b2
Brick9: inception.lab.eng.blr.redhat.com:/rhs/brick3/b3
Brick10: rhs-arch-srv2.lab.eng.blr.redhat.com:/rhs/brick3/b3
Brick11: rhs-arch-srv3.lab.eng.blr.redhat.com:/rhs/brick3/b3
Brick12: rhs-arch-srv4.lab.eng.blr.redhat.com:/rhs/brick4/b4
Brick13: inception.lab.eng.blr.redhat.com:/rhs/brick5/b5
Brick14: rhs-arch-srv2.lab.eng.blr.redhat.com:/rhs/brick5/b5
Brick15: rhs-arch-srv3.lab.eng.blr.redhat.com:/rhs/brick5/b5
Brick16: rhs-arch-srv4.lab.eng.blr.redhat.com:/rhs/brick5/b5
Brick17: inception.lab.eng.blr.redhat.com:/rhs/brick6/b6
Brick18: rhs-arch-srv2.lab.eng.blr.redhat.com:/rhs/brick6/b6
Options Reconfigured:
features.barrier: disable
features.quota-deem-statfs: on
features.inode-quota: on
features.quota: on
features.uss: enable
performance.readdir-ahead: on
Comment 9 errata-xmlrpc 2015-07-29 00:37:33 EDT
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

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