Exception while exporting traces: TypeError: 'NoneType' object cannot be interpreted as an integer

[manuel-koch]

Describe your environment

Python 3.10.9
opentelemetry-api 1.12.0
opentelemetry-exporter-otlp-proto-http 1.12.0
opentelemetry-propagator-b3 1.12.0
opentelemetry-proto 1.12.0
opentelemetry-sdk 1.12.0
opentelemetry-semantic-conventions 0.33b0
backoff. 2.1.2

K9s cluster, exporting traces from a POD to Grafana/Tempo:
docker.io/grafana/tempo:1.3.2
grafana/agent:v0.28.0

Steps to reproduce
The following error is logged on console when the service in the POD tries to export traces:

Python logger is opentelemetry.exporter.otlp.proto.http.trace_exporter and opentelemetry.sdk.trace.export

Transient error Internal Server Error encountered while exporting span batch, retrying in Nones.

Exception while exporting Span batch.
Traceback (most recent call last):
  File \"/usr/local/lib/python3.10/site-packages/opentelemetry/sdk/trace/export/__init__.py\", line 367, in _export_batch
self.span_exporter.export(self.spans_list[:idx])  # type: ignore
  File \"/usr/local/lib/python3.10/site-packages/opentelemetry/exporter/otlp/proto/http/trace_exporter/__init__.py\", line 150, in export
sleep(delay)
TypeError: 'NoneType' object cannot be interpreted as an integer

Likely related to the backoff stuff from

opentelemetry-python/exporter/opentelemetry-exporter-otlp-proto-http/src/opentelemetry/exporter/otlp/proto/http/trace_exporter/__init__.py

Line 60 in edf4d6c

_is_backoff_v2 = next(backoff.expo()) is None

and

opentelemetry-python/exporter/opentelemetry-exporter-otlp-proto-http/src/opentelemetry/exporter/otlp/proto/http/trace_exporter/__init__.py

Line 63 in edf4d6c

def _expo(*args, **kwargs):

What is the expected behavior?

Exporting traces succesfully.

What is the actual behavior?

Opentelemetry functionality causes exception and no traces are exported.

[manuel-koch]

I guess this is fixed with #2980 which seems to be included in Version 1.14.0/0.35b0

[srikanthccv]

I guess this is fixed with #2980 which seems to be included in Version 1.14.0/0.35b0

Yes, this is fixed and released already. Please upgrade and re-open if the issue persists.