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

Details

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

    Description

      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

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. WFLY-12657 KUBE_PING too frequent warning metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-17774 Upgrade jgroups-kubernetes to 1.0.13.Final

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: