Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix(bdd): update the namespace for verifying jiva pods #1649

Merged
merged 1 commit into from
Apr 6, 2020
Merged

fix(bdd): update the namespace for verifying jiva pods #1649

merged 1 commit into from
Apr 6, 2020

Conversation

shubham14bajpai
Copy link
Contributor

Signed-off-by: shubham [email protected]

What this PR does / why we need it:
This PR updates the namespace passed to functions for jiva controller and replica pod checks.

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #

Special notes for your reviewer:

Checklist:

  • Fixes #
  • Labelled this PR & related issue with documentation tag
  • PR messages has document related information
  • Labelled this PR & related issue with breaking-changes tag
  • PR messages has breaking changes related information
  • Labelled this PR & related issue with requires-upgrade tag
  • PR messages has upgrade related information
  • Commit has unit tests
  • Commit has integration tests

kmova
kmova approved these changes Apr 5, 2020
View reviewed changes
Copy link
Contributor

@kmova kmova left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes look good. It will be nice to add the output of running the latest tests to this PR as a comment.

@shubham14bajpai
Copy link
Contributor Author

Changes look good. It will be nice to add the output of running the latest tests to this PR as a comment.

Test result :

mayadata:volume$ ginkgo -v -- -kubeconfig=/var/run/kubernetes/admin.kubeconfig
Running Suite: Test jiva volume provisioning
============================================
Random Seed: 1586078823
Will run 4 of 4 specs

STEP: waiting for maya-apiserver pod to come into running state
STEP: waiting for openebs-provisioner pod to come into running state
STEP: building a namespace
STEP: building a storageclass
STEP: creating a namespace
STEP: creating a storageclass
[jiva] TEST VOLUME PROVISIONING when jiva pvc with replicacount n is created 
  should create 1 controller pod and n replica pod
  /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/volume/provision_test.go:47
STEP: building a pvc
STEP: creating above pvc
STEP: verifying controller pod count
STEP: verifying replica pod count 
STEP: verifying status as bound

• [SLOW TEST:36.057 seconds]
[jiva] TEST VOLUME PROVISIONING
/home/mayadata/work/src/github.com/openebs/maya/tests/jiva/volume/provision_test.go:38
  when jiva pvc with replicacount n is created
  /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/volume/provision_test.go:46
    should create 1 controller pod and n replica pod
    /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/volume/provision_test.go:47
------------------------------
[jiva] TEST VOLUME PROVISIONING when contoller pod is restarted 
  should register replica pods successfully
  /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/volume/provision_test.go:102
STEP: deleting controller pod
STEP: verifying deleted pod is terminated
STEP: verifying controller pod count
STEP: verifying registered replica count and replication factor

• [SLOW TEST:21.687 seconds]
[jiva] TEST VOLUME PROVISIONING
/home/mayadata/work/src/github.com/openebs/maya/tests/jiva/volume/provision_test.go:38
  when contoller pod is restarted
  /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/volume/provision_test.go:101
    should register replica pods successfully
    /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/volume/provision_test.go:102
------------------------------
[jiva] TEST VOLUME PROVISIONING when replica pods is restarted 
  should register replica pods to controller pod successfully
  /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/volume/provision_test.go:149
STEP: deleting replica pods
STEP: verifying deleted pods are terminated
STEP: verifying replica pod count
STEP: verifying registered replica count and replication factor

• [SLOW TEST:25.398 seconds]
[jiva] TEST VOLUME PROVISIONING
/home/mayadata/work/src/github.com/openebs/maya/tests/jiva/volume/provision_test.go:38
  when replica pods is restarted
  /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/volume/provision_test.go:148
    should register replica pods to controller pod successfully
    /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/volume/provision_test.go:149
------------------------------
[jiva] TEST VOLUME PROVISIONING when jiva pvc is deleted 
  should not have any jiva controller and replica pods
  /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/volume/provision_test.go:199
STEP: deleting above pvc
STEP: verifying controller pod count as 0
STEP: verifying replica pod count as 0
STEP: verifying deleted pvc

• [SLOW TEST:21.227 seconds]
[jiva] TEST VOLUME PROVISIONING
/home/mayadata/work/src/github.com/openebs/maya/tests/jiva/volume/provision_test.go:38
  when jiva pvc is deleted
  /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/volume/provision_test.go:198
    should not have any jiva controller and replica pods
    /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/volume/provision_test.go:199
------------------------------
STEP: deleting storageclass
STEP: deleting namespace

Ran 4 of 4 Specs in 104.535 seconds
SUCCESS! -- 4 Passed | 0 Failed | 0 Pending | 0 Skipped
PASS

Ginkgo ran 1 suite in 1m49.663196266s
Test Suite Passed

mayadata:snapshot$ ginkgo -v -- -kubeconfig=/var/run/kubernetes/admin.kubeconfig
Running Suite: Test jiva snapshot provisioning
==============================================
Random Seed: 1586079335
Will run 4 of 4 specs

STEP: waiting for maya-apiserver pod to come into running state
STEP: waiting for openebs-provisioner pod to come into running state
STEP: waiting for openebs-snapshot-operator pod to come into running state
STEP: building a namespace
STEP: building a storageclass
STEP: creating a namespace
STEP: creating a storageclass
[jiva] TEST JIVA SNAPSHOT CREATION when jiva pvc with replicacount n is created 
  should create 1 controller pod and n replica pod
  /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/snapshot/provision_test.go:45
STEP: building a pvc
STEP: creating above pvc
STEP: verifying controller pod count
STEP: verifying replica pod count
STEP: verifying status as bound

• [SLOW TEST:30.963 seconds]
[jiva] TEST JIVA SNAPSHOT CREATION
/home/mayadata/work/src/github.com/openebs/maya/tests/jiva/snapshot/provision_test.go:38
  when jiva pvc with replicacount n is created
  /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/snapshot/provision_test.go:44
    should create 1 controller pod and n replica pod
    /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/snapshot/provision_test.go:45
------------------------------
[jiva] TEST JIVA SNAPSHOT CREATION when jiva snapshot is created 
  should create a snapshot with type ready
  /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/snapshot/provision_test.go:86
STEP: building a snapshot
STEP: creating above snapshot
STEP: verifying type as ready

• [SLOW TEST:5.045 seconds]
[jiva] TEST JIVA SNAPSHOT CREATION
/home/mayadata/work/src/github.com/openebs/maya/tests/jiva/snapshot/provision_test.go:38
  when jiva snapshot is created
  /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/snapshot/provision_test.go:85
    should create a snapshot with type ready
    /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/snapshot/provision_test.go:86
------------------------------
[jiva] TEST JIVA SNAPSHOT CREATION when jiva snapshot is deleted 
  should remove above snapshot
  /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/snapshot/provision_test.go:118
STEP: deleting above snapshot
STEP: verifying deleted snapshot
•
------------------------------
[jiva] TEST JIVA SNAPSHOT CREATION when jiva pvc is deleted 
  should not have any jiva controller and replica pods
  /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/snapshot/provision_test.go:137
STEP: deleting above pvc
STEP: verifying controller pod count as 0
STEP: verifying replica pod count as 0
STEP: verifying deleted pvc

• [SLOW TEST:36.606 seconds]
[jiva] TEST JIVA SNAPSHOT CREATION
/home/mayadata/work/src/github.com/openebs/maya/tests/jiva/snapshot/provision_test.go:38
  when jiva pvc is deleted
  /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/snapshot/provision_test.go:136
    should not have any jiva controller and replica pods
    /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/snapshot/provision_test.go:137
------------------------------
STEP: deleting storageclass
STEP: deleting namespace

Ran 4 of 4 Specs in 74.377 seconds
SUCCESS! -- 4 Passed | 0 Failed | 0 Pending | 0 Skipped
PASS

Ginkgo ran 1 suite in 1m19.217477003s
Test Suite Passed


mayadata:clone$ ginkgo -v -- -kubeconfig=/var/run/kubernetes/admin.kubeconfig --replicas=1
Running Suite: Test jiva clone provisioning
===========================================
Random Seed: 1586084493
Will run 9 of 9 specs

STEP: waiting for maya-apiserver pod to come into running state
STEP: waiting for openebs-provisioner pod to come into running state
STEP: waiting for openebs-snapshot-operator pod to come into running state
STEP: building a namespace
STEP: building a storageclass
STEP: creating a namespace
STEP: creating a storageclass
[jiva] TEST JIVA CLONE CREATION when pvc with replicacount n is created 
  should create 1 controller pod and n replica pod
  /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/clone/provision_test.go:52
STEP: building a pvc
STEP: creating above pvc
STEP: verifying controller pod count
STEP: verifying replica pod count
STEP: verifying status as bound

• [SLOW TEST:10.752 seconds]
[jiva] TEST JIVA CLONE CREATION
/home/mayadata/work/src/github.com/openebs/maya/tests/jiva/clone/provision_test.go:42
  when pvc with replicacount n is created
  /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/clone/provision_test.go:51
    should create 1 controller pod and n replica pod
    /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/clone/provision_test.go:52
------------------------------
[jiva] TEST JIVA CLONE CREATION when creating application pod with above pvc as volume 
  should create a running pod
  /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/clone/provision_test.go:108
STEP: creating pod with above pvc as volume
STEP: verifying pod is running

• [SLOW TEST:11.135 seconds]
[jiva] TEST JIVA CLONE CREATION
/home/mayadata/work/src/github.com/openebs/maya/tests/jiva/clone/provision_test.go:42
  when creating application pod with above pvc as volume
  /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/clone/provision_test.go:107
    should create a running pod
    /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/clone/provision_test.go:108
------------------------------
[jiva] TEST JIVA CLONE CREATION when jiva snapshot is created 
  should create a snapshot with type ready
  /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/clone/provision_test.go:157
STEP: building a snapshot
STEP: creating above snapshot
STEP: verifying type as ready
•
------------------------------
[jiva] TEST JIVA CLONE CREATION when jiva clone pvc is created 
  should create same number of pods as above pvc
  /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/clone/provision_test.go:189
STEP: building a clone pvc
STEP: creating above clone pvc
STEP: verifying clone pod count
STEP: verifying status as bound

• [SLOW TEST:6.835 seconds]
[jiva] TEST JIVA CLONE CREATION
/home/mayadata/work/src/github.com/openebs/maya/tests/jiva/clone/provision_test.go:42
  when jiva clone pvc is created
  /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/clone/provision_test.go:188
    should create same number of pods as above pvc
    /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/clone/provision_test.go:189
------------------------------
[jiva] TEST JIVA CLONE CREATION when creating application pod with above clone pvc as volume 
  should create a running pod
  /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/clone/provision_test.go:239
STEP: creating pod with above pvc as volume
STEP: verifying pod is running

• [SLOW TEST:21.760 seconds]
[jiva] TEST JIVA CLONE CREATION
/home/mayadata/work/src/github.com/openebs/maya/tests/jiva/clone/provision_test.go:42
  when creating application pod with above clone pvc as volume
  /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/clone/provision_test.go:238
    should create a running pod
    /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/clone/provision_test.go:239
------------------------------
[jiva] TEST JIVA CLONE CREATION when verifying data consistency in pvc and clone pvc 
  should have consistent data between the two pvcs
  /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/clone/provision_test.go:297
STEP: fetching data from original pvc
STEP: fetching data from clone pvc
STEP: veryfing data consistency
STEP: deleting application pod
STEP: deleting clone application pod

• [SLOW TEST:11.995 seconds]
[jiva] TEST JIVA CLONE CREATION
/home/mayadata/work/src/github.com/openebs/maya/tests/jiva/clone/provision_test.go:42
  when verifying data consistency in pvc and clone pvc
  /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/clone/provision_test.go:296
    should have consistent data between the two pvcs
    /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/clone/provision_test.go:297
------------------------------
[jiva] TEST JIVA CLONE CREATION when deleting clone pvc 
  should remove clone pvc pods
  /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/clone/provision_test.go:351
STEP: deleting above clone pvc
STEP: verifying clone pvc pods as 0
STEP: verifying deleted clone pvc

• [SLOW TEST:44.433 seconds]
[jiva] TEST JIVA CLONE CREATION
/home/mayadata/work/src/github.com/openebs/maya/tests/jiva/clone/provision_test.go:42
  when deleting clone pvc
  /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/clone/provision_test.go:350
    should remove clone pvc pods
    /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/clone/provision_test.go:351
------------------------------
[jiva] TEST JIVA CLONE CREATION when jiva snapshot is deleted 
  should remove above snapshot
  /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/clone/provision_test.go:379
STEP: deleting above snapshot
STEP: verifying deleted snapshot
•
------------------------------
[jiva] TEST JIVA CLONE CREATION when jiva pvc is deleted 
  should not have any jiva controller and replica pods
  /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/clone/provision_test.go:398
STEP: deleting above pvc
STEP: verifying controller pod count as 0
STEP: verifying replica pod count as 0
STEP: verifying deleted pvc

• [SLOW TEST:13.953 seconds]
[jiva] TEST JIVA CLONE CREATION
/home/mayadata/work/src/github.com/openebs/maya/tests/jiva/clone/provision_test.go:42
  when jiva pvc is deleted
  /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/clone/provision_test.go:397
    should not have any jiva controller and replica pods
    /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/clone/provision_test.go:398
------------------------------
STEP: deleting storageclass
STEP: deleting namespace

Ran 9 of 9 Specs in 127.880 seconds
SUCCESS! -- 9 Passed | 0 Failed | 0 Pending | 0 Skipped
PASS

Ginkgo ran 1 suite in 2m12.328201685s
Test Suite Passed

mayadata:invalidconfig$ ginkgo -v -- -kubeconfig=/var/run/kubernetes/admin.kubeconfig --replicas=1
Running Suite: Test openebs by applying invalid configuration in sc and pvc
===========================================================================
Random Seed: 1586081447
Will run 2 of 2 specs

STEP: Waiting for maya-apiserver pod to come into running state
STEP: Waiting for openebs-provisioner pod to come into running state
[jiva] [-ve] TEST INVALID CAS CONFIGURATIONS IN SC when jiva persistentvolumeclaim referring to invalid storageclass is applied 
  should not create Jiva controller and replica pods
  /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/invalidconfig/invalidconfig_test.go:99
STEP: building a namespace
STEP: building a storageclass
STEP: building a persistentvolumeclaim
STEP: creating a namespace
STEP: creating a storageclass
STEP: creating a persistentvolumeclaim
STEP: verifying controller pod count
STEP: verifying replica pod count
STEP: deleting persistentvolumeclaim
STEP: deleting storageclass
STEP: deleting namespace

• [SLOW TEST:344.313 seconds]
[jiva] [-ve] TEST INVALID CAS CONFIGURATIONS IN SC
/home/mayadata/work/src/github.com/openebs/maya/tests/jiva/invalidconfig/invalidconfig_test.go:50
  when jiva persistentvolumeclaim referring to invalid storageclass is applied
  /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/invalidconfig/invalidconfig_test.go:98
    should not create Jiva controller and replica pods
    /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/invalidconfig/invalidconfig_test.go:99
------------------------------
[jiva] [-ve] TEST INVALID CONFIGURATIONS IN persistentvolumeclaim when We apply invalid persistentvolumeclaim yaml in k8s cluster 
  PVC creation should give error because of invalid pvc yaml
  /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/invalidconfig/invalidconfig_test.go:180
STEP: building a namespace
STEP: building a storageclass
STEP: building a persistentvolumeclaim
STEP: creating a namespace
STEP: createing a storageclass
STEP: create PVC named {jiva-invalid-config-volume-claim} in Namespace: {validation-ns2}
STEP: deleting persistentvolumeclaim
STEP: deleting storageclass
STEP: deleting namespace
•
Ran 2 of 2 Specs in 350.060 seconds
SUCCESS! -- 2 Passed | 0 Failed | 0 Pending | 0 Skipped
PASS

Ginkgo ran 1 suite in 5m55.008583925s
Test Suite Passed


mayadata:node-selector$ ginkgo -v -- -kubeconfig=/var/run/kubernetes/admin.kubeconfig --replicas=1
Running Suite: Test jiva volume node selector
=============================================
Random Seed: 1586083737
Will run 2 of 2 specs

STEP: waiting for maya-apiserver pod to come into running state
STEP: waiting for openebs-provisioner pod to come into running state
STEP: building a namespace
STEP: building a storageclass
STEP: creating above namespace
STEP: creating above storageclass
STEP: listing ready nodes
STEP: verifying minimum node count to be 2
STEP: labeling node 1 as app
STEP: labeling node 2 as storage
[jiva] TEST NODE SELECTOR when replica pod of pvc is restarted 
  should stick to storage node after reconciliation
  /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/node-selector/node_selector_test.go:126
STEP: building a pvc
STEP: creating above pvc
STEP: verifying controller pod count
STEP: verifying replica pod count 
STEP: verifying status as bound
STEP: deleting a replica pod
STEP: verifying deleted pod is terminated
STEP: verifying running replica pod count 
STEP: verifying replica node selector
STEP: deleting a replica pod
STEP: verifying deleted pod is terminated
STEP: verifying running replica pod count 
STEP: verifying replica node selector
STEP: deleting a replica pod
STEP: verifying deleted pod is terminated
STEP: verifying running replica pod count 
STEP: verifying replica node selector
STEP: deleting a replica pod
STEP: verifying deleted pod is terminated
STEP: verifying running replica pod count 
STEP: verifying replica node selector
STEP: deleting a replica pod
STEP: verifying deleted pod is terminated
STEP: verifying running replica pod count 
STEP: verifying replica node selector
STEP: deleting above pvc
STEP: verifying controller pod count as 0
STEP: verifying replica pod count as 0
STEP: verifying deleted pvc

• [SLOW TEST:99.225 seconds]
[jiva] TEST NODE SELECTOR
/home/mayadata/work/src/github.com/openebs/maya/tests/jiva/node-selector/node_selector_test.go:37
  when replica pod of pvc is restarted
  /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/node-selector/node_selector_test.go:125
    should stick to storage node after reconciliation
    /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/node-selector/node_selector_test.go:126
------------------------------
[jiva] TEST NODE SELECTOR when controller pod of pvc is restarted 
  should stick to app node after reconciliation
  /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/node-selector/node_selector_test.go:174
STEP: building a pvc
STEP: creating above pvc
STEP: verifying controller pod count
STEP: verifying replica pod count 
STEP: verifying status as bound
STEP: deleting a controller pod
STEP: verifying deleted pod is terminated
STEP: verifying running controller pod count 
STEP: verifying target node selector
STEP: deleting a controller pod
STEP: verifying deleted pod is terminated
STEP: verifying running controller pod count 
STEP: verifying target node selector
STEP: deleting a controller pod
STEP: verifying deleted pod is terminated
STEP: verifying running controller pod count 
STEP: verifying target node selector
STEP: deleting a controller pod
STEP: verifying deleted pod is terminated
STEP: verifying running controller pod count 
STEP: verifying target node selector
STEP: deleting a controller pod
STEP: verifying deleted pod is terminated
STEP: verifying running controller pod count 
STEP: verifying target node selector
STEP: deleting above pvc
STEP: verifying controller pod count as 0
STEP: verifying replica pod count as 0
STEP: verifying deleted pvc

• [SLOW TEST:101.914 seconds]
[jiva] TEST NODE SELECTOR
/home/mayadata/work/src/github.com/openebs/maya/tests/jiva/node-selector/node_selector_test.go:37
  when controller pod of pvc is restarted
  /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/node-selector/node_selector_test.go:173
    should stick to app node after reconciliation
    /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/node-selector/node_selector_test.go:174
------------------------------
STEP: removing label from node 1
STEP: removing label from node 2
STEP: deleting storageclass
STEP: deleting namespace

Ran 2 of 2 Specs in 211.395 seconds
SUCCESS! -- 2 Passed | 0 Failed | 0 Pending | 0 Skipped
PASS

Ginkgo ran 1 suite in 3m37.629717803s
Test Suite Passed


mayadata:node-stickiness$ ginkgo -v -- -kubeconfig=/var/run/kubernetes/admin.kubeconfig
Running Suite: Test jiva volume node stickiness
===============================================
Random Seed: 1586079725
Will run 1 of 1 specs

STEP: waiting for maya-apiserver pod to come into running state
STEP: waiting for openebs-provisioner pod to come into running state
STEP: building a namespace
STEP: building a storageclass
STEP: creating above namespace
STEP: creating above storageclass
[jiva] TEST NODE STICKINESS when replica pod of pvc is deleted 
  should stick to same node after reconciliation
  /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/node-stickiness/node_stickiness_test.go:107
STEP: building a pvc
STEP: creating above pvc
STEP: verifying controller pod count
STEP: verifying replica pod count 
STEP: verifying status as bound
STEP: deleting a replica pod
STEP: verifying deleted pod is terminated
STEP: verifying running replica pod count 
STEP: verifying node stickiness
STEP: deleting a replica pod
STEP: verifying deleted pod is terminated
STEP: verifying running replica pod count 
STEP: verifying node stickiness
STEP: deleting a replica pod
STEP: verifying deleted pod is terminated
STEP: verifying running replica pod count 
STEP: verifying node stickiness
STEP: deleting a replica pod
STEP: verifying deleted pod is terminated
STEP: verifying running replica pod count 
STEP: verifying node stickiness
STEP: deleting a replica pod
STEP: verifying deleted pod is terminated
STEP: verifying running replica pod count 
STEP: verifying node stickiness
STEP: deleting above pvc
STEP: verifying controller pod count as 0
STEP: verifying replica pod count as 0
STEP: verifying deleted pvc

• [SLOW TEST:168.790 seconds]
[jiva] TEST NODE STICKINESS
/home/mayadata/work/src/github.com/openebs/maya/tests/jiva/node-stickiness/node_stickiness_test.go:37
  when replica pod of pvc is deleted
  /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/node-stickiness/node_stickiness_test.go:106
    should stick to same node after reconciliation
    /home/mayadata/work/src/github.com/openebs/maya/tests/jiva/node-stickiness/node_stickiness_test.go:107
------------------------------
STEP: deleting storageclass
STEP: deleting namespace

Ran 1 of 1 Specs in 168.934 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
PASS

Ginkgo ran 1 suite in 2m56.074351575s
Test Suite Passed

mittachaitu
mittachaitu approved these changes Apr 6, 2020
View reviewed changes
Copy link

@mittachaitu mittachaitu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes are good

prateekpandey14
prateekpandey14 approved these changes Apr 6, 2020
View reviewed changes
Copy link
Contributor

@prateekpandey14 prateekpandey14 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@prateekpandey14 prateekpandey14 merged commit 0557ba7 into openebs-archive:master Apr 6, 2020
@shubham14bajpai shubham14bajpai deleted the jiva-bdd branch October 12, 2020 05:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@mittachaitu mittachaitu mittachaitu approved these changes

@kmova kmova kmova approved these changes

@prateekpandey14 prateekpandey14 prateekpandey14 approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@shubham14bajpai @prateekpandey14 @kmova @mittachaitu