Short description
When running OPA with the distributed tracing option enabled, we get the following error when the server is stopped.
Failed to shutdown `OpenTelemetry` trace exporter gracefully.
Steps To Reproduce
- Get the latest version of
opa (I've tried with version 0.62 and the latest version)
./opa_linux_amd64 version
Version: 0.63.0-dev
Build Commit: d3a4a87f506dec744ed93177c37bea5e2afa186b
Build Timestamp: 2024-03-27T19:08:00Z
Build Hostname: nico-Latitude-7420
Go Version: go1.21.0
Platform: linux/amd64
WebAssembly: available
- Run the following command line
./opa_linux_amd64 run --server --set distributed_tracing.type=grpc
- Kill the process (Ctrl + C works fine)
- The full output should looks like that
./opa_linux_amd64 run --server --set distributed_tracing.type=grpc
{"addrs":[":8181"],"diagnostic-addrs":[],"level":"info","msg":"Initializing server. OPA is running on a public (0.0.0.0) network interface. Unless you intend to expose OPA outside of the host, binding to the localhost interface (--addr localhost:8181) is recommended. See https://www.openpolicyagent.org/docs/latest/security/#interface-binding","time":"2024-03-28T09:18:37+01:00"}
^C{"level":"info","msg":"Shutting down...","time":"2024-03-28T09:18:38+01:00"}
{"level":"info","msg":"Server shutdown.","time":"2024-03-28T09:18:38+01:00"}
{"err":"context canceled","level":"error","msg":"Failed to shutdown OpenTelemetry trace exporter gracefully.","time":"2024-03-28T09:18:38+01:00"}
Expected behavior
The OpenTelemetry trace exporter should be gracefully shut down, and no error should be seen.
Additional context
We have seen this error appeared after upgrading OPA from version 0.59 to 0.62.
Short description
When running OPA with the distributed tracing option enabled, we get the following error when the server is stopped.
Steps To Reproduce
opa(I've tried with version 0.62 and the latest version)Expected behavior
The
OpenTelemetrytrace exporter should be gracefully shut down, and no error should be seen.Additional context
We have seen this error appeared after upgrading OPA from version 0.59 to 0.62.