| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
| |
In jenkins right after peer probe, add brick function is
failing with peer not in cluster. So having check for the
peer to be connected or not then proceed to next step.
Change-Id: I73bf92819ad44f7a6a14795ab07c45d260cd04eb
Signed-off-by: Bala Konda Reddy M <bmekala@redhat.com>
|
|
|
In this test case we are checking whether the peer status is having
FQDN or not.
Steps followed are:
1. Peer probe to a new node i.e., N1 to N2 using hostname
2. Check peer status in N2, it should have FQDN of N1
3. Check peer status on N1, it should have FQDN of N2
4. Create a distributed volume with single brick on each node.
5. Start volume
6. Peer probe to a new node N3 using IP
7. Add a brick from node3 to the volume, add brick should succeed.
8. Get volume info, it should have correct information
Change-Id: I7f2bb8cecf28e61273ca83d7e3ad502ced979c5c
Signed-off-by: Sanju Rakonde <srakonde@redhat.com>
|
