Uploaded image for project: 'OpenShift Logging'
  1. OpenShift Logging
  2. LOG-2161

Cronjob elasticsearch-im-prune-app keeps recreating after enabling delete by query

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • Logging 5.4.0
    • Logging 5.4.0
    • Log Storage
    • None
    • False
    • False
    • NEW
    • VERIFIED
    • Logging (LogExp) - Sprint 213

    Description

      Description of problem:

      The cronjob elasticsearch-im-prune-app keeps recreating after enabling delete by query.

      $ oc get cj
      NAME                         SCHEDULE       SUSPEND   ACTIVE   LAST SCHEDULE   AGE
      elasticsearch-im-app         */15 * * * *   False     0        18s             35m
      elasticsearch-im-audit       */15 * * * *   False     0        18s             35m
      elasticsearch-im-infra       */15 * * * *   False     0        18s             35m
      elasticsearch-im-prune-app   */10 * * * *   False     0        <none>          1s
      $ oc get cj
      NAME                         SCHEDULE       SUSPEND   ACTIVE   LAST SCHEDULE   AGE
      elasticsearch-im-app         */15 * * * *   False     0        19s             35m
      elasticsearch-im-audit       */15 * * * *   False     0        19s             35m
      elasticsearch-im-infra       */15 * * * *   False     0        19s             35m
      elasticsearch-im-prune-app   */10 * * * *   False     0        <none>          0s 

      Version-Release number of selected component (if applicable):

      cluster-logging.5.4.0-37

      elasticsearch-operator.5.4.0-50

      How reproducible:

      Always

      Steps to Reproduce:
      1. deploy logging with:

      apiVersion: "logging.openshift.io/v1"
      kind: "ClusterLogging"
      metadata:
        name: "instance"
        namespace: "openshift-logging"
      spec:
        managementState: "Managed"
        logStore:
          type: "elasticsearch"
          retentionPolicy: 
            application:
              maxAge: 6h
              namespaceSpec:
              - minAge: 10m
                namespace: project-1
              - minAge: 20m
                namespace: project-2
              pruneNamespacesInterval: 10m
            infra:
              maxAge: 3h
            audit:
              maxAge: 1d
          elasticsearch:
            nodeCount: 3
            redundancyPolicy: "SingleRedundancy"
            resources:
              requests:
                cpu: 1
                memory: "2Gi"
            storage:
              storageClassName: "gp2"
              size: "20Gi"
        visualization:
          type: "kibana"
          kibana:
            replicas: 1
        collection:
          logs:
            type: "fluentd"
            fluentd: {} 

      2. check cronjob status
      3.

      Actual results:

      Expected results:

      The cronjob elasticsearch-im-prune-app should be kept just like the cj/elasticsearch-im-app

      Additional info:

      Attachments

        Issue Links

          Activity

            People

              sasagarw@redhat.com Sashank Agarwal (Inactive)
              qitang@redhat.com Qiaoling Tang
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: