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

[Vector] vector container can't start due to "unknown field `pod_annotation_fields`" .

XMLWordPrintable

    • Logging (Core) - Sprint 220

      Description of problem:

      The vector container is in CrashLoopBackOff status, get below error in the log:

      Jun 08 03:30:01.845  INFO vector::app: Log level is enabled. level="info"
      Jun 08 03:30:01.845  INFO vector::app: Loading configs. path=[("/etc/vector/vector.toml", Some(Toml))]
      Jun 08 03:30:01.847 ERROR vector::cli: Configuration error. error=unknown field `pod_annotation_fields`, expected one of `extra_label_selector`, `self_node_name`, `extra_field_selector`, `auto_partial_merge`, `data_dir`, `annotation_fields`, `exclude_paths_glob_patterns`, `max_read_bytes`, `max_line_bytes`, `glob_minimum_cooldown_ms`, `ingestion_timestamp_field`, `timezone`, `kube_config_file` for key `sources.raw_container_logs` at line 189 column 1

       

      I tried to update:

      pod_annotation_fields.pod_labels = "kubernetes.labels"
      pod_annotation_fields.pod_namespace = "kubernetes.namespace_name"
      pod_annotation_fields.pod_annotations = "kubernetes.annotations"
      pod_annotation_fields.pod_uid = "kubernetes.pod_id"
      pod_annotation_fields.pod_node_name = "hostname" 

      to:

      annotation_fields.pod_labels = "kubernetes.labels"
      annotation_fields.pod_namespace = "kubernetes.namespace_name"
      annotation_fields.pod_annotations = "kubernetes.annotations"
      annotation_fields.pod_uid = "kubernetes.pod_id"
      annotation_fields.pod_node_name = "hostname" 

      then the vector reports:

      Jun 08 05:10:50.727 ERROR vector::cli: Configuration error. error=unknown field `pod_annotations`, expected one of `pod_name`, `pod_namespace`, `pod_uid`, `pod_ip`, `pod_ips`, `pod_labels`, `pod_node_name`, `container_name`, `container_id`, `container_image` for key `sources.raw_container_logs` at line 189 column 1 

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

      cluster-logging.5.5.0-5  

      How reproducible:

      Always

      Steps to Reproduce:
      1. subscribe CLO and EO
      2. deploy logging stack, using vector as the collector

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

      3. check logging pods status

      Actual results:

      Collector pods are in CrashLoopBackOff status

      Expected results:

      All pods could be running

      Additional info: 

            vimalkum@redhat.com Vimal Kumar
            qitang@redhat.com Qiaoling Tang
            Qiaoling Tang Qiaoling Tang
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: