| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Problem:
The default value of performance.io-cache was ON by default
before gluster 6.0, in gluster 6.0 it was set to OFF.
Solution:
Adding code to check gluster version and then check
weather it is ON or OFF as shown below:
```
if get_gluster_version(self.mnode) >= 6.0:
self.assertIn("off", ret['performance.io-cache'],
"io-cache value is not correct")
else:
self.assertIn("on", ret['performance.io-cache'],
"io-cache value is not correct")
```
CentOS-CI failure analysis:
This patch is expected to failed as if we run `gluster --version` on
nightly builds the output returned as shown below:
```
# gluster --version
glusterfs 20200220.a0e0890
Repository revision: git://git.gluster.org/glusterfs.git
Copyright (c) 2006-2016 Red Hat, Inc. <https://www.gluster.org/>
GlusterFS comes with ABSOLUTELY NO WARRANTY.
It is licensed to you under your choice of the GNU Lesser
General Public License, version 3 or any later version (LGPLv3
or later), or the GNU General Public License, version 2 (GPLv2),
in all cases as published by the Free Software Foundation.
```
This output can't be parsed by get_gluster_version() function
which is used in this patch to get the gluster version
and check for perfromance.io-cache's default value accordingly.
Change-Id: I00b652a9d5747cbf3006825bb17b9ca2f69cb9cd
Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
|
|
|
|
|
| |
Change-Id: I1395e14d8d0aa0cc6097e51c64262fb481f36f05
Signed-off-by: Valerii Ponomarov <kiparis.kh@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The error message which is displayed when we do a gluster v get
for options which don't exist has been changed. Adding a if based
logic which can check for the old as well as the new error message.
Old msg:
volume get option: failed: Did you mean auth.allow or ...reject?
New msg:
volume get option: failed: Did you mean ctime.noatime?
Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
Change-Id: I9496d391a7da9dba64d3426a024c2b1b68455f20
|
|
|
|
| |
Change-Id: I46fc2feffe6443af6913785d67bf310838532421
|
|
|
|
| |
Change-Id: I14609030983d4485dbce5a4ffed1e0353e3d1bc7
|
|
volume get functionalities
Test steps:
1. Create a gluster cluster
2. Get the option from the non-existing volume,
# gluster volume get <non-existing vol> io-cache
3. Get all options from the non-existing volume,
# gluster volume get <non-existing volume > all
4. Provide a incorrect command syntax to get the options
from the volume
# gluster volume get <vol-name>
# gluster volume get
# gluster volume get io-cache
5. Create any type of volume in the cluster
6. Get the value of the non-existing option
# gluster volume get <vol-name> temp.key
7. get all options set on the volume
# gluster volume get <vol-name> all
8. get the specific option set on the volume
# gluster volume get <vol-name> io-cache
9. Set an option on the volume
# gluster volume set <vol-name> performance.low-prio-threads 14
10. Get all the options set on the volume and check
for low-prio-threads
# gluster volume get <vol-name> all | grep -i low-prio-threads
11. Get all the options set on the volume
# gluster volume get <vol-name> all
12. Check for any cores in "cd /"
Change-Id: Ifd7697e68d7ecf297d7be75680a5681686c51ca0
Signed-off-by: Rajesh Madaka <rmadaka@redhat.com>
|