Skip to content

Tracing is broken with v1.7.16 #10358

Closed as not planned
Closed as not planned
@ugur99

Description

Description

When we upgrade containerd from 1.7.15 to 1.7.16 we noticed that our tracing config is broken; we saw some errors in the containerd log that implies no endpoint is configured; but same config works with the previous version.

Steps to reproduce the issue

Describe the results you received and expected

related part of container config

  [plugins."io.containerd.internal.v1.tracing"]
    sampling_ratio = 1.0
    service_name = "containerd"

  [plugins."io.containerd.tracing.processor.v1.otlp"]
    endpoint = "0.0.0.0:4317"
    insecure = true
    protocol = "grpc"

containerd 1.7.15 logs

Jun 18 12:58:19 node1 containerd[136137]: time="2024-06-18T12:58:19.949185303Z" level=info msg="loading plugin \"io.containerd.tracing.processor.v1.otlp\"..." type=io.containerd.tracing.processor.v1
Jun 18 12:58:19 node1 containerd[136137]: time="2024-06-18T12:58:19.949558011Z" level=info msg="loading plugin \"io.containerd.internal.v1.tracing\"..." type=io.containerd.internal.v1

containerd 1.7.16 logs

Jun 18 12:49:10 node1 containerd[1368693]: time="2024-06-18T12:49:10.388645358Z" level=info msg="loading plugin \"io.containerd.tracing.processor.v1.otlp\"..." type=io.containerd.tracing.processor.v1
Jun 18 12:49:10 node1 containerd[1368693]: time="2024-06-18T12:49:10.388679435Z" level=info msg="skip loading plugin \"io.containerd.tracing.processor.v1.otlp\"..." error="skip plugin: tracing endpoint not configured" type=io.containerd.tracing.processor.v1
Jun 18 12:49:10 node1 containerd[1368693]: time="2024-06-18T12:49:10.388697817Z" level=info msg="loading plugin \"io.containerd.internal.v1.tracing\"..." type=io.containerd.internal.v1
Jun 18 12:49:10 node1 containerd[1368693]: time="2024-06-18T12:49:10.388722405Z" level=info msg="skip loading plugin \"io.containerd.internal.v1.tracing\"..." error="skip plugin: tracing endpoint not configured" type=io.containerd.internal.v1

I checked the changelog and saw that there was some work done to deprecate this config; could it be related to this commit?

What version of containerd are you using?

1.7.16

Any other relevant information

No response

Show configuration if it is related to CRI plugin.

No response

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions