Description

When restarting containerd service via systemd, the system log always showed that containerd failed to init the tracing processor but it is acctually not set on the containerd config.

Oct 17 17:07:02 autovm containerd[26489]: time="2022-10-17T17:07:02.711558915+08:00" level=error msg="failed to initialize a tracing processor \"otlp\"" error="no OpenTelemetry endpoint: skip plugin"

Steps to reproduce the issue

1. Start containerd v1.6.6 or newer via systemd
2. restart containerd service by executing systemctl restart containerd
3. check system log by executing journalctl -u containerd

Describe the results you received and expected

If the plugin is not loaded, containerd should not pop out the error that failed to init it, instead, it should print a message to skip this error

Here is the PR for reviewing: #7541

What version of containerd are you using?

containerd github.com/containerd/containerd v1.6.6 10c1295

Any other relevant information

No response

Show configuration if it is related to CRI plugin.

No response