)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"03acc2889188b1696a914491369750a753d2f60b","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"7152d6bc_31f4e7fe","updated":"2025-08-20 05:09:38.000000000","message":"recheck fix in https://review.opendev.org/c/openstack/kayobe/+/957886 merged. also unstable debian upgrade still","commit_id":"fcaafd8817d7218103b7e234ed6aef6ea45f930d"},{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"e1426f0318b6b5162617fa221c750096d96cb666","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"d4ee0271_1f73dbd7","updated":"2025-08-19 13:23:00.000000000","message":"we try to reduce the number of jobs we need, so adding additional jobs is a bit counter-productive. would having this as experimental job maybe be enough?\n\nI addition as a reviewer, since I know nothing about kayobe jobs, I would always ignore results from this job anyway, since I could not tell whether errors are related to a change or not","commit_id":"fcaafd8817d7218103b7e234ed6aef6ea45f930d"},{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"f4d6c57f794a67fc9c85c963e1bb46b178eafa9a","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"d4219e16_33bd42d9","in_reply_to":"468630c9_eb5ace8c","updated":"2025-08-20 05:12:36.000000000","message":"yes, periodic won\u0027t help much. maybe we can go with this change and watch for a while whether it actually helps","commit_id":"fcaafd8817d7218103b7e234ed6aef6ea45f930d"},{"author":{"_account_id":15197,"name":"Pierre Riteau","email":"pierre@stackhpc.com","username":"priteau","status":"StackHPC"},"change_message_id":"c80bd44691e3d9a048a8c609980d6413e657e377","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"468630c9_eb5ace8c","in_reply_to":"712c3ba5_59f73ac4","updated":"2025-08-19 17:12:39.000000000","message":"Actually a periodic job would only catch issues once the kolla-ansible patch has been merged. We would like to spot them before the changes merge.","commit_id":"fcaafd8817d7218103b7e234ed6aef6ea45f930d"},{"author":{"_account_id":15197,"name":"Pierre Riteau","email":"pierre@stackhpc.com","username":"priteau","status":"StackHPC"},"change_message_id":"d98e1ee7c40c118c7b546cbcbd0685569cc95488","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"88950834_6ad55876","in_reply_to":"d4219e16_33bd42d9","updated":"2025-08-21 07:49:55.000000000","message":"Maybe we could limit it to changes to specific files? We often break on inventory group changes or major changes in globals.yml variables.","commit_id":"fcaafd8817d7218103b7e234ed6aef6ea45f930d"},{"author":{"_account_id":15197,"name":"Pierre Riteau","email":"pierre@stackhpc.com","username":"priteau","status":"StackHPC"},"change_message_id":"26dbd1269f5094335beeb315adaedb800f1df26d","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"712c3ba5_59f73ac4","in_reply_to":"d4ee0271_1f73dbd7","updated":"2025-08-19 16:35:09.000000000","message":"I understand your concerns, and partially share them. The main goal is to catch when kolla-ansible changes are breaking kayobe, to quickly apply a fix in Kayobe, or revert the change in kolla-ansible if it is clearly broken.\n\nOf course, we would need people to be watching the results and ready to report/fix the issue to kayobe.\n\nI am concerned that an experimental job would not be run frequently enough to have much benefit. What about a nightly periodic job?","commit_id":"fcaafd8817d7218103b7e234ed6aef6ea45f930d"}]}