Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[exporter/zipkin] Correctness test failure: TestTracingGoldenData/otlp-zipkin #33715

Open
crobert-1 opened this issue Jun 21, 2024 · 4 comments
Labels

Comments

@crobert-1
Copy link
Member

Component(s)

exporter/zipkin

Describe the issue you're reporting

Failing CI/CD action

Failure output:

=== RUN   TestTracingGoldenData/otlp-zipkin
2024/06/21 15:48:44 
receivers:
  otlp:
    protocols:
      grpc:
        endpoint: "127.0.0.1:41143"
exporters:
  zipkin:
    endpoint: http://127.0.0.1:45711/api/v2/spans
    format: json
processors:
  
  batch:
    send_batch_size: 1024



extensions:

service:
  telemetry:
    metrics:
      address: 127.0.0.1:[457](https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/9616271927/job/26525416353?pr=33694#step:7:458)11
  extensions:
  pipelines:
    traces:
      receivers: [otlp]
      processors: [batch]
      exporters: [zipkin]

2024/06/21 15:48:44 Starting mock backend...
2024-06-21T15:48:44.322Z	info	service@v0.103.0/service.go:115	Setting up own telemetry...
2024-06-21T15:48:44.322Z	info	service@v0.103.0/telemetry.go:96	Serving metrics	{"address": "127.0.0.1:45711", "level": "Normal"}
2024-06-21T15:48:44.323Z	info	service@v0.103.0/service.go:182	Starting otelcol...	{"Version": "latest", "NumCPU": 4}
2024-06-21T15:48:44.323Z	info	extensions/extensions.go:34	Starting extensions...
2024-06-21T15:48:44.323Z	info	otlpreceiver@v0.103.0/otlp.go:102	Starting GRPC server	{"kind": "receiver", "name": "otlp", "data_type": "traces", "endpoint": "127.0.0.1:41143"}
2024-06-21T15:48:44.323Z	info	service@v0.103.0/service.go:208	Everything is ready. Begin running and processing data.
2024-06-21T15:48:44.323Z	warn	localhostgate/featuregate.go:63	The default endpoints for all servers in components will change to use localhost instead of 0.0.0.0 in a future version. Use the feature gate to preview the new default.	{"feature gate ID": "component.UseLocalHostAsDefaultHost"}
2024-06-21T15:48:44.323Z	error	otelcol@v0.103.0/collector.go:320	Asynchronous error received, terminating process	{"error": "listen tcp 127.0.0.1:45711: bind: address already in use"}
go.opentelemetry.io/collector/otelcol.(*Collector).Run
	/home/runner/go/pkg/mod/go.opentelemetry.io/collector/otelcol@v0.103.0/collector.go:320
github.com/open-telemetry/opentelemetry-collector-contrib/testbed/testbed.(*inProcessCollector).Start.func2
	/home/runner/work/opentelemetry-collector-contrib/opentelemetry-collector-contrib/testbed/testbed/in_process_collector.go:80
2024-06-21T15:48:44.323Z	info	service@v0.103.0/service.go:245	Starting shutdown...
2024-06-21T15:48:44.323Z	info	extensions/extensions.go:59	Stopping extensions...
2024-06-21T15:48:44.323Z	info	service@v0.103.0/service.go:259	Shutdown complete.
2024/06/21 15:48:45 unable to start, otelcol state is 3
    test_case.go:289: unable to start, otelcol state is 3
2024/06/21 15:48:45 Starting load generator at 1024 items/sec.
2024/06/21 15:48:45 Stopped generator. Sent:         0 traces (0/sec)
2024/06/21 15:48:45 Stopping mock backend...
2024/06/21 15:48:45 Stopped backend. Received:         0 items (0/sec)

Looks like this is the offending part:

2024-06-21T15:48:44.323Z	error	otelcol@v0.103.0/collector.go:320	Asynchronous error received, terminating process	{"error": "listen tcp 127.0.0.1:45711: bind: address already in use"}
go.opentelemetry.io/collector/otelcol.(*Collector).Run
	/home/runner/go/pkg/mod/go.opentelemetry.io/collector/otelcol@v0.103.0/collector.go:320
github.com/open-telemetry/opentelemetry-collector-contrib/testbed/testbed.(*inProcessCollector).Start.func2
	/home/runner/work/opentelemetry-collector-contrib/opentelemetry-collector-contrib/testbed/testbed/in_process_collector.go:80
@crobert-1 crobert-1 added the needs triage New item requiring triage label Jun 21, 2024
Copy link
Contributor

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@crobert-1
Copy link
Member Author

@TylerHelmuth
Copy link
Member

Experienced this today during the release

Copy link
Contributor

github-actions bot commented Sep 2, 2024

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants