# No online node found with volume replica

**URL:** <https://forums.portworx.com/t/no-online-node-found-with-volume-replica/830>\
**Category:** Portworx on Kubernetes\
**Created:** [March 5, 2021, 9:34am UTC](https://forums.portworx.com/t/no-online-node-found-with-volume-replica/830 "2021-03-05T09:34:18Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![lindaorny](https://yyz2.discourse-cdn.com/flex030/user_avatar/forums.portworx.com/lindaorny/32/314_2.png) [@lindaorny](https://forums.portworx.com/u/lindaorny)\
**Post date:** [March 5, 2021, 9:34am UTC](https://forums.portworx.com/t/no-online-node-found-with-volume-replica/830/1 "2021-03-05T09:34:18Z")

</div>

I am installing Kafka on top of Portworx using the below manual:

> **[How to Run HA Kafka with Rancher Kubernetes Engine - Portworx](https://portworx.com/run-ha-kafka-rancher-kubernetes-engine/)**
>
> This tutorial is a walk-through of the steps involved in deploying and managing a highly available Kafka cluster on Kubernetes as a StatefulSet with Rancher Kubernetes Engine.

However, it stuck at pending when building the zookeeper pod zk-0. The kubectl describe output of the pod is  
Warning FailedScheduling 4m1s (x46 over 9m33s) stork Failed filter with extender at URL [http://stork-service.kube-system:8099/filter](http://stork-service.kube-system:8099/filter), code 400  
Warning FailedScheduling 3m34s (x26 over 9m33s) stork No online node found with volume replica  
Warning FailedScheduling 115s (x26 over 9m26s) stork No online node found with volume replica

The three worker nodes has three devices. They are /dev/vda, /dev/vdb, /dev/vdc where /dev/vdb is configured for kvdb and vdc is reserved for portworx volume. I have created MySQL and it mounts at /dev/vdc with no problem.

**Storage Class**  
NAME PROVISIONER AGE  
portworx-sc [kubernetes.io/portworx-volume](http://kubernetes.io/portworx-volume) 73m  
portworx-sc-rep3 [kubernetes.io/portworx-volume](http://kubernetes.io/portworx-volume) 73m

**Persistent Volume**  
NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE  
pvc-821d4f45-7d8b-11eb-97f2-fa163e839485 5Gi RWO Delete Bound default/datadir-zk-0 portworx-sc 72m  
pvc-ae95ce47-7d8c-11eb-97f2-fa163e839485 5Gi RWO Delete Bound default/datadir-zk-2 portworx-sc 63m  
pvc-fead296a-7d8b-11eb-97f2-fa163e839485 5Gi RWO Delete Bound default/datadir-zk-1 portworx-sc 69m

**Persistent Volume Claim**  
datadir-zk-0 Bound pvc-821d4f45-7d8b-11eb-97f2-fa163e839485 5Gi RWO portworx-sc 74m  
datadir-zk-1 Bound pvc-fead296a-7d8b-11eb-97f2-fa163e839485 5Gi RWO portworx-sc 70m  
datadir-zk-2 Bound pvc-ae95ce47-7d8c-11eb-97f2-fa163e839485 5Gi RWO portworx-sc 65m

Could I know how to resolve the issue…?

Thanks.