Why gluster pod take longer time to get into READY state in OCS 3.9 ?

Solution Verified - Updated -

Issue

  • Why gluster pod fail to get into READY state after pod deletion ?
  • The oc get pods -o wide showing one of the pod in not-READY state

    NAME                      READY     STATUS    RESTARTS   AGE       IP              NODE
    glusterfs-storage-skw49   0/1       Running   1          24m       10.0.0.2   rhnode02.rhtest.com
    glusterfs-storage-9skdh   1/1       Running   1          1h        10.0.0.1   rhnode01.rhtest.com
    glusterfs-storage-aaa12   1/1       Running   1          6d        10.0.0.3   rhnode03.rhtest.com
    

Environment

  • Red Hat Enterprise Linux 7.x
  • Red Hat Enterprise 3.4
  • Openshift Containter Storage 3.9

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content