| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
| |
Change-Id: Ic14be81f1cd42c470d2bb5c15505fc1bc168a393
Signed-off-by: Valerii Ponomarov <kiparis.kh@gmail.com>
|
|
|
|
|
| |
Change-Id: I7a76e0c2e491caffd7ba1b648b47c4c6a687c89a
Signed-off-by: Valerii Ponomarov <kiparis.kh@gmail.com>
|
|
|
|
|
| |
Change-Id: I5a60646b984557ed024cb4b3a8088ce7dfb7622c
Signed-off-by: Valerii Ponomarov <kiparis.kh@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This test case verifies that disruption during full heal
doesn't result in data corruption.
Testcase steps:
1.Create IO from mountpoint.
2.Calculate arequal from mount.
3.Delete data from backend from the EC volume.
4.Trigger heal full.
5.Disable Heal.
6.Again Enable and do Heal full.
7.Reboot a Node.
8.Calculate arequal checksum and compare it.
Change-Id: I1fac53df30106ff98fdd270b210aca90a53a1ac5
Co-authored-by: Sunil Kumar Acharya <sheggodu@redhat.com>
Signed-off-by: Sunil Kumar Acharya <sheggodu@redhat.com>
Signed-off-by: Karan Sandha <ksandha@redhat.com>
Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
|
|
|
|
|
| |
Change-Id: Ie408d7972452123b63eb5cc17c61bc319a99e304
Signed-off-by: Valerii Ponomarov <kiparis.kh@gmail.com>
|
|
|
|
|
| |
Change-Id: Iae0f6e729c26e466d82c4133439bdd7021485e7f
Signed-off-by: Valerii Ponomarov <kiparis.kh@gmail.com>
|
|
|
|
|
| |
Change-Id: Ieecf4707ee6cb7b3c58380306bf105e282986b1b
Signed-off-by: Valerii Ponomarov <kiparis.kh@gmail.com>
|
|
|
|
|
| |
Change-Id: Iafa09988617e2e29942aa6ceb003eac2ddf2b561
Signed-off-by: ubansal <ubansal@redhat.com>
|
|
|
|
|
| |
Change-Id: Id4df838565ec3f9ad765cf223bb5115e43dac1c5
Signed-off-by: Valerii Ponomarov <kiparis.kh@gmail.com>
|
|
|
|
|
| |
Change-Id: I56194047ac6105cddb43d3f413b03bcdbbcde587
Signed-off-by: Valerii Ponomarov <kiparis.kh@gmail.com>
|
|
|
|
|
| |
Change-Id: I39ed09ee91a345daae7bb675184a8a30d48575fa
Signed-off-by: Valerii Ponomarov <kiparis.kh@gmail.com>
|
|
|
|
|
| |
Change-Id: I308f95d16ac18ec80c5c78aac9152d9ae41449bb
Signed-off-by: Valerii Ponomarov <kiparis.kh@gmail.com>
|
|
|
|
|
| |
Change-Id: I5b36fe5144ebca05d17fb14e05b5dc75c63f7a29
Signed-off-by: Valerii Ponomarov <kiparis.kh@gmail.com>
|
|
|
|
|
| |
Change-Id: I1c568a43bb635720a4aedc75ba844a4f499130fe
Signed-off-by: Valerii Ponomarov <kiparis.kh@gmail.com>
|
|
|
|
|
| |
Change-Id: I97bcbc3f9b75129be833ffa7def1b00cfd32a474
Signed-off-by: ubansal <ubansal@redhat.com>
|
|
|
|
|
| |
Change-Id: I8b8aad4c3e4a2ad924478f1842498289323b7098
Signed-off-by: Valerii Ponomarov <kiparis.kh@gmail.com>
|
|
|
|
|
| |
Change-Id: I5c9693008d0f26dda2a51916ee9a637b310f4d5d
Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Test case:
- check if brick multiplex is disable by default
- check for warning message triggering by setting brick-multiplex and
choosing 'n' in y/n
- check if brick multiplex is disabled after triggering warning message
- check brick multiplex for all possible statuses
(positive and negative)
- check for brick multiplex status in /var/lib/glusterd/options file
Change-Id: If1f2cba0b932837716f577bd6c4d113659975f91
Co-authored-by: Vitalii Koriakov <vkoriako@redhat.com>
Signed-off-by: Vitalii Koriakov <vkoriako@redhat.com>
Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Earlier arguments passed to function log_volume_info_and_status
in the code were (self.mnode, self.volume), which is incorrect.
The function takes arguments as (mnode, volname). Changing the
second incorrect argument self.volume to self.volname for the
function log_volume_info_and_status at all its occurances in the
code.
Change-Id: If9bca96679f37c2d7cbcf0f34a16df8549110e21
Signed-off-by: sayaleeraut <saraut@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Adding the default configurations for arbiter and
distributed- arbiter volume types, as it was missing from the
gluster_base_class.py.
Adding Arbiter and Distributed arbiter configuration in the
glusto_tests_config.yml
Change-Id: Ic078505975ff1a1171a4bc6ee6ad2c67f0fb45f1
Signed-off-by: sayaleeraut <saraut@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Following changes were implemented:
- Delete unused imports and place used ones in the alphabetical order.
Imports are splitted into 3 groups: built-ins, third-parties and
local modules/libs.
- Make changes to support py3 in addition to py2.
- Minimize number of code lines keeping the same behaviour and improving
readability.
- Add possibility to get 'bound' (cls) methods using 'get_super_method'
staticmethod from base class. Before it was possible to call only
unbound (self) methods.
- Update 'test_add_brick.py' module as PoC for running base class bound
methods in both - py2 and py3. Now this module py2/3 compatible.
Change-Id: I1b66b3a91084b2487c26bec8763ab2b4e12ac482
Signed-off-by: Valerii Ponomarov <kiparis.kh@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Lots of test classes are wrapped by the 'runs_on' decorator.
This decorator replaces original test class with it's copy where
parent class is original test class if we use py3.
Such situation leads to the impossibility to use following approach in
py3:
super(SomeClass, some_class_instance).some_method()
And, the above approach is py2/3 compatible approach for calling
parent class's methods.
The problem we face is that we fall into the unexpected recursion here.
So, add 'get_super_method' to the base class, which detects such
situation and returns proper method of a proper parent class.
Also, fix test class located at 'glusterd/test_peer_status.py' module
to have proof of concept.
With this change 'test_peer_probe_status' test case becomes completely
py2/3 compatible.
Example of new method usage:
@runs_on([['distributed'], ['glusterfs']])
class TestDecoratedClass(GlusterBaseClass):
...
def setUp(self):
self.get_super_method(self, 'setUp')()
...
This approach must be used instead of existing calls of 'im_func'
function if we want to support both at once - python2 and python3.
Signed-off-by: Valerii Ponomarov <kiparis.kh@gmail.com>
Change-Id: I23f4462b64f9d4dd90812273f08fb756d073ab76
|
|
|
|
|
|
|
|
| |
Dict attribute called "iteritems()" is not supported in the py3.
So, replace it's usage with another similar attr called "items()".
Change-Id: I130b7f67f0a2d5da5ed6c3d792f5ff024ba148f4
Signed-off-by: Valerii Ponomarov <kiparis.kh@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
The tearDown function was incomplete where, since the test case has
enabled the shared storage, it needs to be disabled as part of the
tear down.
This fix includes the addition of the necessary tearDown parts along
with some cosmetic changes.
Change-Id: Id421c840a1c7606ecf185c9520ca436d47911f45
Signed-off-by: Vinayak Papnoi <vpapnoi@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As the below mentioned bug is fixed resubmitting testcase:
https://bugzilla.redhat.com/show_bug.cgi?id=1690753
Test case:
-> Creating two volumes and starting them, stop the second volume
-> Set the server quorum and set the ratio to 90
-> Stop the glusterd in one of the node, so the quorum won't meet
-> Peer probing a new node should fail
-> Volume stop will fail
-> Volume delete will fail
-> Volume reset will fail
-> Start the glusterd on the node where it is stopped
-> Volume stop, start, delete will succeed once quorum is met
Change-Id: Ic9dea44364d4cb84b6170eb1f1cfeff1398b7a9b
Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
|
|
|
|
|
|
|
| |
Change-Id: I12b5586bdcef128df64fcd8a0ba80f193395f313
Co-authored-by: Vijay Avuthu <vavuthu@redhat.com>
Signed-off-by: Vijay Avuthu <vavuthu@redhat.com>
Signed-off-by: Milind Waykole <milindwaykole96@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Test case:
* Enable quota on the volume.
* Set hard and soft time out to zero.
* Create some files and directories from mount point
so that the limits are reached.
* Perform add-brick operation on the volume.
* Start rebalance on the volume.
* While rebalance is running, kill one of the bricks of
the volume and start after a while.
* While rebalance + self heal is in progress,
create some more files and directories from the mount point until
limit is hit.
Change-Id: Ic7d2ac92b4e132ab1018242c17bed5e888e86cf3
Co-authored-by: Sanoj Unnikrishnan <sunnikri@redhat.com>
Signed-off-by: Sanoj Unnikrishnan <sunnikri@redhat.com>
Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Test statvfs calls return appropriate avaialable size with quota.
* Enable Quota
* Save the result from statvfs call
* Set Quota limit of 1 GB on the root of the volume
* Validate statvfs call honors quota
* Remove quota limit from the Volume
* Validate statvfs call reports old value of avialable space
Change-Id: I5f6271e0acdba13d483eb321f62ca9fdc5360859
Signed-off-by: Sanoj Unnikrishnan <sunnikri@redhat.com>
Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
|
|
|
|
|
|
|
|
|
| |
Adding test case to check posix compliance
for nfs ganesha
Change-Id: I8188fba9245cfe27ae30b7818cfe7d2b624e9d87
Signed-off-by: Ambarish Soman <asoman@redhat.com>
Signed-off-by: Arjun Sharma <arjsharm@redhat.com>
|
|
|
|
| |
Change-Id: Iec8471de0add8cb6eaf6c80fb24c631e992aad4d
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Earlier in the testcase we were turning off shd
which is not correct and we have to turn off only
client side heal options as mentioned below
metadata-self-heal
entry-self-heal
data-self-heal
After renaming files we have to turn on these options
while doing a look up from client
Change-Id: I8c76abb8e79620c412e5991f5d8255b6b2a850e8
Signed-off-by: Milind Waykole <milindwaykole96@gmail.com>
|
|
|
|
|
| |
Change-Id: I2afd326fe0df1959a8fd20bc7325159688c1a73e
Signed-off-by: Jilju Joy <jijoy@redhat.com>
|
|
|
|
|
|
|
|
|
|
| |
Add-brick command failure is leaving the directories created
on the backend bricks which is resulting in the failure of the
subsequent cases.
Added some changes to clean the bricks.
Change-Id: I108efbcaef2010f6fd52c334446059f96fff3741
Signed-off-by: Prasad Desala <tdesala@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
-> Create volume
-> Stop the volume
-> Enabling serve quorum
-> start the volume
-> Set server quorum ratio to 95%
-> Stop the glusterd of any one of the node
-> Perform rebalance operation operation
-> Check gluster volume status
-> start glusterd
Change-Id: I3bb42a83414dbcabdc61178e11d584eaf90c3b40
Signed-off-by: Rajesh Madaka <rmadaka@redhat.com>
|
|
|
|
|
|
|
|
|
| |
In a few testcases in glusterd count++ is missing due to which the
testcase in an infinite loop. Fixing that and sending patch.
Change-Id: I56a355f6ea3ae79231e09d7aee80031da3ebec52
Signed-off-by: yinkui <13965432176@163.com>
Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
|
|
|
|
|
|
| |
Change-Id: I7f8769defd34d55d8eec720c40ed55e69523f917
Signed-off-by: Anees Patel <anepatel@redhat.com>
Signed-off-by: milindw96 <milindwaykole96@gmail.com>
|
|
|
|
|
|
|
|
|
| |
Since the NfsGaneshaVolumeBaseClass has been removed
the ACL test needs to be modified to use the alternative
method to the above mentioned class.
Change-Id: I398dfef6dd334a3e3f3871d44705af312d81318a
Signed-off-by: Arjun Sharma <arjsharm@redhat.com>
|
|
|
|
|
|
|
|
|
| |
* The issue with disperse and distributed-disperse volume types are now fixed.
* Reference : Bugzilla 1663375
* Using mount object instead of clients list for setting authentication
Change-Id: I914cee7fb790dc65e947e0b6db40d02e23575e65
Signed-off-by: Jilju Joy <jijoy@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Earlier in nfs_ganesha_ops, two library functions
enable_acl, disable_acl were implemented and later
with changes to NFS Ganesha Base class both the
functions are removed and made into single function
set_acl.
Change-Id: I5456adeeffa49c35a5ea19c8d11272f91ec4bdbf
Signed-off-by: Bala Konda Reddy M <bmekala@redhat.com>
|
|
|
|
|
|
| |
Change-Id: Ifef2ffe022accf59edcbc949c505f47931b19fe4
Signed-off-by: Anees Patel <anepatel@redhat.com>
Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
|
|
|
|
|
| |
Change-Id: I5372caf852b41e127c46f6afa697435dcde9dbf6
Signed-off-by: Jilju Joy <jijoy@redhat.com>
|
|
|
|
|
| |
Change-Id: I40e36e1d4d404fcb9709fa9e50d33cad77172350
Signed-off-by: Jilju Joy <jijoy@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Steps
1. Start IO on mount points
2. Add bricks to expand the volume
3. Start rebalance and wait for its completion
4. Validate IOs
Change-Id: I97c09c9fc226afeff1446d225959730715f89aef
Signed-off-by: Jilju Joy <jijoy@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Steps
1. Start IO on mount points
2. Create another volume 'volume_new'
3. Export volume_new through nfs-ganesha
4. Mount the volume on clients
Change-Id: I2c4fe59e9a85e6668672d31a0a6c27d11c7f03f8
Signed-off-by: Jilju Joy <jijoy@redhat.com>
|
|
|
|
|
| |
Change-Id: I3fb826bd0ecbe46bee4b9f8594b23f16921adbec
Signed-off-by: Arjun Sharma <arjsharm@redhat.com>
|
|
|
|
|
|
|
|
|
| |
With redundancy count as negative or disperse count
with negative(different permutations) and disperse
data count equal to disperse count
Change-Id: I761851c64833256532464f56a9a78e20ceb8a4e1
Signed-off-by: ubansal <ubansal@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The test case 'test_client_side_quorum_with_fixed_validate_max_bricks'
does not have a tearDown part where the volume options which have been
set inside the test case have not been reset to default.
The library function 'set_volume_options' was being imported from a
wrong library. This fix includes this change along with the tearDown
steps.
Change-Id: Ic57494e7a7e8a25303b7979f98cc2dfbc9a7d7b6
Signed-off-by: Vinayak Papnoi <vpapnoi@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For each node should have one self heal daemon and
one quota daemon should be up running
that means total number of self heal daemon and quota daemon
to be up and ruuning is (number of nodes *2),
in code i am checking that count should
be equalent to (number of nodes * 2)
Change-Id: I79d40467edc255a479a369f19a6fd1fec9111f53
Signed-off-by: Rajesh Madaka <rmadaka@redhat.com>
Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
The ExecutionError msg at line 66 should be "failed to clean-up
volume" because it is under tearDownClass. The g.log.info msg
at line 123 should be "Checking if gfid xattr of directories is
displayed and is same on all the bricks on the server node" as the
code below it checks for the gfid xattr on the bricks on server
node and not if it is displayed on mount point.
Change-Id: If4e20e3487a44c1cc7047504d19cc9859424ccd4
Signed-off-by: sayaleeraut <saraut@redhat.com>
|
|
|
|
|
| |
Change-Id: I240ecb0b4a9c99134b7a5cd237a59c2857d0fb7b
Signed-off-by: yinkui <13965432176@163.com>
|