{"task": {"agent_timeout": 3000, "task": "codegen__jaegertracing__jaeger-6790", "verifier_timeout": 3000, "instruction": "This is a code generation task. You are expected to write working code that solves the described problem.\n<issue>\n      ### What happened?\n\nI use helm chart with the images (cronjobs) jaeger-es-index-cleaner:1.57.0 and jaeger-es-rollover:1.57.0.\nThe rollover creates a new span every hour (for example). But the index cleaner only removes indexes older than 00:00 hours (once a day). And I would like indexes older than 24 hours to be deleted from the moment the index cleaner is launched. That is, 08:00, 09:00 and so on.\nHere is the index cleaner log\n```\n{\n  \"level\": \"info\",\n  \"ts\": 1732172114.3503263,\n  \"caller\": \"es-index-cleaner/main.go:89\",\n  \"msg\": \"Indices before this date will be deleted\",\n  \"date\": \"2024-11-17T00:00:00Z\"\n}\n```\n\n### Steps to reproduce\n\nCreate cronjob jaeger-es-rollover whith `'{\"max_age\": \"1h\"}'` and run it every hour.\nRun jaeger-es-index-cleaner every hour.\n\n### Expected behavior\n\nIndexes are deleted every hour, not once a day\n\n### Relevant log output\n\n```shell\n\n```\n\n### Screenshot\n\n_No response_\n\n### Additional context\n\n_No response_\n\n### Jaeger backend version\n\n1.57.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>\nFocus on implementing the required functionality correctly and efficiently. Treat this as a programming challenge.\nYou are not allowed to read git history.\n", "memory": "8192m", "runnable": false, "difficulty": "hard", "language": "", "cpus": "", "instruction_truncated": false, "category": "code-generation", "compose": false, "has_solution": true, "oracle": null, "docker_image": "", "taskset": "devopsgym", "tags": ["code-generation", "devops-bench"]}, "runs": []}