Description of problem: logging-curator couldn't be started when .regex is set in configmap Version-Release number of selected component (if applicable): openshift3/logging-curator/images/v3.10.0-0.30.0.0 How reproducible: always Steps to Reproduce: 1. Deploy logging 2. Add .regex policy in logging-curator configmap [anli@upg_slave_qeos10 310anli]$ oc get configmap logging-curator -o yaml apiVersion: v1 data: config.yaml: | myapp-dev: delete: days: 1 .operations: delete: weeks: 1 .defaults: delete: days: 7 runhour: 05 runminute: 16 timezone: America/New_York .regex: - pattern: '^project\..+\-dev.*\..*$' delete: days: 31 - pattern: '.*prod.*\..*$' delete: months: 1 kind: ConfigMap metadata: creationTimestamp: 2018-04-27T07:39:30Z name: logging-curator namespace: openshift-logging resourceVersion: "35413" selfLink: /api/v1/namespaces/openshift-logging/configmaps/logging-curator uid: 1ee133b6-49ee-11e8-908e-0e6d82bcf43c 3. watch the logging-curator pod status $ oc logs logging-curator-3-nfj9w The project name must match this regex: [^[a-z0-9]([-a-z0-9]*[a-z0-9])?$] This does not match: [.regex] Actual results: [anli@upg_slave_qeos10 310anli]$ oc get pods NAME READY STATUS RESTARTS AGE logging-curator-3-nfj9w 0/1 CrashLoopBackOff 7 14m Expected results: The pod can be started and the policy are used when delete index. Additional info:
v3.10.0-0.30.0.0 doesn't have the latest code. I checked and the most recent image (v3.10.0-0.32.0.0) also has old code. I'll let u know once this is fixed.
Waiting the latest images
Anli: v3.10.0-0.37.0.0 has all that's needed
verified on v3.10.0-0.38.0
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:1816