Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-17771

KUBE_PING too frequent warning metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • 7.3.0.CD18
    • 7.3.0.CD18
    • Clustering
    • None

      In my test application on openshift KUBE_PING logs warning every 20-30s .

      13:27:05,340 WARN  [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
      13:27:40,600 WARN  [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-52,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
      13:27:40,600 WARN  [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-52,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
      13:27:57,892 WARN  [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-52,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
      13:27:57,892 WARN  [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-52,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
      13:28:21,104 WARN  [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
      13:28:21,104 WARN  [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
      13:28:45,737 WARN  [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-52,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
      13:28:45,737 WARN  [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-52,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
      13:29:05,335 WARN  [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
      13:29:05,335 WARN  [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
      13:29:29,027 WARN  [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
      13:29:29,027 WARN  [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
      13:30:04,195 WARN  [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
      13:30:04,195 WARN  [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
      

              rhn-engineering-rhusar Radoslav Husar
              msimka@redhat.com Martin Simka
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: