{"task": {"agent_timeout": 3000, "task": "testgen__jaegertracing__jaeger-7395", "verifier_timeout": 3000, "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.\n<issue>\n      ### What happened?\n\nUsing v1.66.0\nThe PR [6270](https://github.com/jaegertracing/jaeger/commit/1a0922779595060dd542ffb0ec913697cde7f3d0#diff-7a032f882c800dde77a50447562dbc3404aad1f2dd95de96bd69cd9d14e3df88L45-R47), change the way to load TLS on kafka.\nPreviously with kafka.[producer,consumer].authentication=plaintext if kafka.[producer,consumer].tls.enabled, `|| config.TLS.Enabled` was loading `setTLSConfiguration`.\n\nThe new code only loads TLS when authentication=tls, failing the connection with other authentication (plaintext/kerberos) + TLS (does not upgrade to TLS during authentication).\nBasically it has become impossible to configure SASL-SSL with PLAIN.\n\n### Steps to reproduce\n\n1. Run jaeger-collector/jaeger-ingester with kafka + TLS producer/consumer enabled and authentification = plaintext (kerberos is probably also impacted).\n2. Crash to connect to remote kafka.\n3. See Relevant log output\n\n### Expected behavior\n\nIt should work as before.\n\n### Relevant log output\n\n```shell\nFeb 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\"}\n\nFeb 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\"}\n```\n\n### Screenshot\n\n_No response_\n\n### Additional context\n\n_No response_\n\n### Jaeger backend version\n\nv1.66.0\n\n### SDK\n\n_No response_\n\n### Pipeline\n\n_No response_\n\n### Stogage backend\n\n_No response_\n\n### Operating system\n\n_No response_\n\n### Deployment model\n\n_No response_\n\n### Deployment configs\n\n```shell\n\n```\n\n</issue>\nPlease generate test cases that check whether an implemented solution resolves the issue of the user (at the top, within <issue/> brackets).\nYou may apply changes to several files.\nApply as much reasoning as you please and see necessary.\nMake sure to implement only test cases and don't try to fix the issue itself.\nYou are not allowed to read git history.\n", "memory": "8192m", "runnable": false, "difficulty": "hard", "language": "", "cpus": "", "instruction_truncated": false, "category": "test-generation", "compose": false, "has_solution": true, "oracle": null, "docker_image": "", "taskset": "devopsgym", "tags": ["test-generation", "devops-bench"]}, "runs": []}