# devopsgym / testgen__jaegertracing__jaeger-7368

- taskset: [devopsgym](https://harnessreport.com/tasks/devopsgym.md)
- difficulty: hard
- category: test-generation
- language: 
- runnable from the site: no
- agent timeout: 3000s

## Results by harness

_none yet_

## Instruction

```
The following text contains a user issue (in <issue/> brackets) posted at a repository. Further, you are provided with file contents of several files in the repository that contain relevant code (in <code> brackets). It may be necessary to use code from third party dependencies or files not contained in the attached documents however. Your task is to identify the issue and implement a test case that verifies a proposed solution to this issue. More details at the end of this text.
<issue>
      ### What happened?

Using v1.66.0
The PR [6270](https://github.com/jaegertracing/jaeger/commit/1a0922779595060dd542ffb0ec913697cde7f3d0#diff-7a032f882c800dde77a50447562dbc3404aad1f2dd95de96bd69cd9d14e3df88L45-R47), change the way to load TLS on kafka.
Previously with kafka.[producer,consumer].authentication=plaintext if kafka.[producer,consumer].tls.enabled, `|| config.TLS.Enabled` was loading `setTLSConfiguration`.

The new code only loads TLS when authentication=tls, failing the connection with other authentication (plaintext/kerberos) + TLS (does not upgrade to TLS during authentication).
Basically it has become impossible to configure SASL-SSL with PLAIN.

### Steps to reproduce

1. Run jaeger-collector/jaeger-ingester with kafka + TLS producer/consumer enabled and authentification = plaintext (kerberos is probably also impacted).
2. Crash to connect to remote kafka.
3. See Relevant log output

### Expected behavior

It should work as before.

### Relevant log output

```shell
Feb 17 15:47:19 infra-2.local docker-compose[3961324]: jaeger-collector_1  | {"level":"fatal","ts":1739807239.7673259,"caller":"collector/main.go:75","msg":"Failed to init storage factory","error":"kafka: client has run out of available brokers to talk to: 5 errors occurred:\n\t* EOF\n\t* unexpected EOF\n\t* dial tcp: address broker-004.local:9091broker-005.local:9091: too many colons in address\n\t* unexpected EOF\n\t* unexpected EOF\n","stacktrace":"main.main.func1\n\tgithub.com/jaegertracing/jaeger/cmd/collector/main.go:75\ngithub.com/spf13/cobra.(*Command).execute\n\tgithub.com/spf13/cobra@v1.8.1/command.go:985\ngithub.com/spf13/cobra.(*Command).ExecuteC\n\tgithub.com/spf13/cobra@v1.8.1/command.go:1117\ngithub.com/spf13/cobra.(*Command).Execute\n\tgithub.com/spf13/cobra@v1.8.1/command.go:1041\nmain.main\n\tgithub.com/jaegertracing/jaeger/cmd/collector/main.go:152\nruntime.main\n\truntime/proc.go:272"}

Feb 17 15:49:08 infra-2.local docker-compose[3964107]: jaeger-ingester_1   | {"level":"fatal","ts":1739807348.9089887,"caller":"ingester/main.go:72","msg":"Unable to create consumer","error":"kafka: client has run out of available brokers to talk to: 5 errors occurred:\n\t* unexpected EOF\n\t* unexpected EOF\n\t* EOF\n\t* dial tcp: address broker-004.local:9091broker-005.local:9091: too many colons in address\n\t* unexpected EOF\n","stacktrace":"main.main.func1\n\tgithub.com/jaegertracing/jaeger/cmd/ingester/main.go:72\ngithub.com/spf13/cobra.(*Command).execute\n\tgithub.com/spf13/cobra@v1.8.1/command.go:985\ngithub.com/spf13/cobra.(*Command).ExecuteC\n\tgithub.com/spf13/cobra@v1.8.1/command.go:1117\ngithub.com/spf13/cobra.(*Command).Execute\n\tgithub.com/spf13/cobra@v1.8.1/command.go:1041\nmain.main\n\tgithub.com/jaegertracing/jaeger/cmd/ingester/main.go:108\nruntime.main\n\truntime/proc.go:272"}
```

### Screenshot

_No response_

### Additional context

_No response_

### Jaeger backend version

v1.66.0

### SDK

_No response_

### Pipeline

_No response_

### Stogage backend

_No response_

### Operating system

_No response_

### Deployment model

_No response_

### Deployment configs

```shell

```

</issue>
Please generate test cases that check whether an implemented solution resolves the issue of the user (at the top, within <issue/> brackets).
You may apply changes to several files.
Apply as much reasoning as you please and see necessary.
Make sure to implement only test cases and don't try to fix the issue itself.
You are not allowed to read git history.
```
---
Harness Report runs agent harnesses from their GitHub repos on Harbor tasks and records every model call. Every page is also `.md` and `.json`; index: https://harnessreport.com/llms.txt · MCP: https://harnessreport.com/mcp