Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-21

OCP 4.9 - Different metadata.generateName generated for the Cronjob pods

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Normal Normal
    • None
    • 4.9
    • Unknown
    • Low
    • None
    • False
    • Hide

      None

      Show
      None

      We have noticed that OCP 4.9.x (all 4.9 releases) is creating the pods with a different nomenclature for all of them generated by the Cronjobs. Note: This is not observed on OCP 4.8 and 4.10.

      Example

      Instead of:  image-pruner-27620820-d49vt

      It's adding the characters '-1' in between the ID and the random string:

      image-pruner-27620820--1-d49vt

       

      While this appears to be non-critical to the operation of the cluster, this behavior was raised by one of our customers after upgrading the cluster from 4.8 to 4.9. As they use regex to parse the pods name during log collection, this new behavior affected when checking the pods name and consequently loss of log events.

       

      Reference:
      https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status:~:text=see%20here.-,Idempotency,-All%20compatible%20Kubernetes

              Unassigned Unassigned
              rhn-support-faldana Fabio Aldana
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: