Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-14340

`Infinispan.status.podStatus` spec shows incorrect pod names for the real deployment topology

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 14.0.4.Final
    • 14.0.2.Final
    • Operator
    • None
    • Hide

      Deploy a simple Infinispan definition similar to:

       

      apiVersion: infinispan.org/v1 
kind: Infinispan 
metadata:
  name: sp-cache-infinispan
spec:
  replicas: 3
  service:
    type: DataGrid
    container:
      ephemeralStorage: true
  logging:
    categories:
      org.infinispan: info
      org.jgroups: info
  expose:
    type: Route
  security:
    endpointAuthentication: false
    authorization:
      enabled: false
    endpointEncryption:
      type: None  

      This definition will deploy the following pods:

      ❯ oc get pod
NAME                                                   READY   STATUS    RESTARTS   AGE
sp-cache-infinispan-0                                  1/1     Running   0          84s
sp-cache-infinispan-1                                  1/1     Running   0          72s
sp-cache-infinispan-2                                  1/1     Running   0          62s
sp-cache-infinispan-config-listener-5654b4d6f7-d2wrh   1/1     Running   0          37s

      The `Infinispan.status.podStatus` shows:

      status:
  # ...
  podStatus:
    ready:
    - sp-cache-infinispan-1
    - sp-cache-infinispan-2
    - sp-cache-infinispan-3

      The right information must be:

      status:
  # ...
  podStatus:
    ready:
    - sp-cache-infinispan-0
    - sp-cache-infinispan-1
    - sp-cache-infinispan-2

       

      Show
      Deploy a simple Infinispan definition similar to:   apiVersion: infinispan.org/v1  kind: Infinispan  metadata:   name: sp-cache-infinispan spec:   replicas: 3   service:     type: DataGrid     container:       ephemeralStorage: true   logging:     categories:       org.infinispan: info       org.jgroups: info   expose:     type: Route   security:     endpointAuthentication: false     authorization:       enabled: false     endpointEncryption:       type: None   This definition will deploy the following pods: ❯ oc get pod NAME                                                   READY   STATUS    RESTARTS   AGE sp-cache-infinispan-0                                  1/1     Running   0          84s sp-cache-infinispan-1                                  1/1     Running   0          72s sp-cache-infinispan-2                                  1/1     Running   0          62s sp-cache-infinispan-config-listener-5654b4d6f7-d2wrh   1/1     Running   0          37s The `Infinispan.status.podStatus` shows: status:   # ...   podStatus:     ready:     - sp-cache-infinispan-1     - sp-cache-infinispan-2     - sp-cache-infinispan-3 The right information must be: status:   # ...   podStatus:     ready:     - sp-cache-infinispan-0     - sp-cache-infinispan-1     - sp-cache-infinispan-2  
    • Compatibility/Configuration, User Experience

      The DataGrid operator creates a `StatefulSet` to manage the life cycle of the DataGrid pods. The `StatefulSet` creates pods using an index to identify each of them from the topology, always starting from zero.

      The current `status` definition of the `Infinispan` CR includes a list of status for each pod of the deployment, however, that list is not showing the real names of the pods. There is no correlation between both entries.

      The `Infinispan` CR shows the following information:

      ❯ oc get infinispan sp-cache-infinispan -o yaml
# ...
status:
  # ...
  podStatus:
    ready:
    - sp-cache-infinispan-1
    - sp-cache-infinispan-2
    - sp-cache-infinispan-3
  statefulSetName: sp-cache-infinispan

      However, the pods already deployed and ready are:

      ❯ oc get pod
NAME                                                   READY   STATUS    RESTARTS   AGE
sp-cache-infinispan-0                                  1/1     Running   0          84s
sp-cache-infinispan-1                                  1/1     Running   0          72s
sp-cache-infinispan-2                                  1/1     Running   0          62s
sp-cache-infinispan-config-listener-5654b4d6f7-d2wrh   1/1     Running   0          37s

      If that information is not aligned can produce issues in some automate process to check the status of the different objects (`Infinispan` CR and pods). That information must be the same and use the right naming convention from the `StatefulSet`.

              vrigamon@redhat.com Vittorio Rigamonti
              rmarting@redhat.com Roman Martin Gil
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: