)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":33765,"name":"Mridula Joshi","email":"mrjoshi@redhat.com","username":"mrjoshi"},"change_message_id":"d7f20363c0656406c95caaf4687589bfd1f58f96","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"0401fc58_acb0273f","updated":"2022-09-20 07:24:52.000000000","message":"recheck","commit_id":"eab45e41236750113ee06bc2556c71c345239d44"},{"author":{"_account_id":33765,"name":"Mridula Joshi","email":"mrjoshi@redhat.com","username":"mrjoshi"},"change_message_id":"87841a99fb6afc3b0e4d6ca4ed633fa0a2de7c77","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"4b1b8646_3208e850","updated":"2022-09-19 11:38:44.000000000","message":"recheck","commit_id":"eab45e41236750113ee06bc2556c71c345239d44"},{"author":{"_account_id":28223,"name":"Cedric Jeanneret","display_name":"cjeanner (Tengu)","email":"cjeanner@redhat.com","username":"cjeanner"},"change_message_id":"4bdee65107ab515eeda7ae6509555de2b90d14d0","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"283d5f43_c15ae9ee","updated":"2022-09-26 10:00:02.000000000","message":"(though it seems to miss a bit the LP content, since it was pointing  at the DB purge, which apparently can\u0027t be added to train)","commit_id":"51c26676f917a59df4aa6aba271e5ae8cf814580"},{"author":{"_account_id":21129,"name":"Alan Bishop","email":"abishopsweng@gmail.com","username":"ASBishop","status":"ex Red Hat"},"change_message_id":"a7c5293114129251f853ca2d62ffa7666d5236ca","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":5,"id":"b8549c38_8c2e5077","in_reply_to":"283d5f43_c15ae9ee","updated":"2022-09-28 16:40:35.000000000","message":"Right, and so that leaves me confused. The cron job was specifically added to purge the DB, so I don\u0027t know what the cron job will be doing in train, where apparently DB purge isn\u0027t supported. What is the cron job doing now? I think that should be clarified in the commit msg.","commit_id":"51c26676f917a59df4aa6aba271e5ae8cf814580"},{"author":{"_account_id":19138,"name":"Pranali Deore","email":"pdeore@redhat.com","username":"PranaliD"},"change_message_id":"d7b9ee5ed0f7a046db65b8fcc8b66c9e1cfa77a5","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":5,"id":"3d31efb9_27e30d43","in_reply_to":"b8549c38_8c2e5077","updated":"2022-09-29 06:17:00.000000000","message":"In train, cache pruner doesn\u0027t run even though it\u0027s there in the cron file generated by puppet. As the new \u0027glance_api_cron\u0027 container executes the cache jobs as well, this backport has only \u0027glance_api_cron\u0027 container changes \u0026 db purge changes are skipped(db purge support is not there in train).\n\nBasically, glance_api_cron container runs both db purge jobs and cache jobs,\nit processes all cron jobs defined in the glance config directory,\nthe cron file for both db purge and cache cleaner/pruner are stored in the\nsame directory, /var/lib/config-data/puppet-generated/glance_api/var/spool/cron/\n\nHope this helps :)\n\n@mridula, kindly please update the commit message with the reason behind partial backport.","commit_id":"51c26676f917a59df4aa6aba271e5ae8cf814580"},{"author":{"_account_id":28223,"name":"Cedric Jeanneret","display_name":"cjeanner (Tengu)","email":"cjeanner@redhat.com","username":"cjeanner"},"change_message_id":"a2f117e54d7c4185e037522a1ddad40b73847bce","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":7,"id":"72181fe4_0aa0ece2","updated":"2022-09-30 07:26:18.000000000","message":"Thanks for the detailed explanation.","commit_id":"067510228af6db0d4588237033b91b6948d2b4bc"}],"releasenotes/notes/glance-db-purge-bb185353a45880c7.yaml":[{"author":{"_account_id":13861,"name":"yatin","email":"ykarel@redhat.com","username":"yatinkarel"},"change_message_id":"580087bd7b109210dadc80b128e5deaaf98dd569","unresolved":true,"context_lines":[{"line_number":2,"context_line":"features:"},{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    The ``glance_api_cron`` container has been introduced, which executes db"},{"line_number":5,"context_line":"    purge job for Glance service. Use GlanceCronDbPurge* parameters to override"},{"line_number":6,"context_line":"    cron parameters."}],"source_content_type":"text/x-yaml","patch_set":5,"id":"22acb9b0_892ee8d8","line":6,"range":{"start_line":5,"start_character":4,"end_line":6,"end_character":1},"updated":"2022-09-28 12:21:43.000000000","message":"this looks invalid now due to partial backport.","commit_id":"51c26676f917a59df4aa6aba271e5ae8cf814580"}]}