)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":28048,"name":"Will Szumski","email":"will@stackhpc.com","username":"jovial"},"change_message_id":"05fb20dd12ec4b6c910d3550fbf8e393b76fc4b4","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"19d60c0f_2de9475c","updated":"2025-01-23 09:59:24.000000000","message":"Happy for this to be tweaked in a future patch","commit_id":"9c6b4477f84b9360eafe88fe26a3dd230b0f7c50"},{"author":{"_account_id":35263,"name":"Matt Crees","email":"mattc@stackhpc.com","username":"mattcrees"},"change_message_id":"db935a7648b0534e933b9b436f1ba4c0bed1e898","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"7ea82d03_e35a0f23","updated":"2025-01-30 13:44:09.000000000","message":"I\u0027m happy to merge this now so we can fix the CI failures. Let\u0027s follow up on the open comments later","commit_id":"9c6b4477f84b9360eafe88fe26a3dd230b0f7c50"},{"author":{"_account_id":15197,"name":"Pierre Riteau","email":"pierre@stackhpc.com","username":"priteau","status":"StackHPC"},"change_message_id":"cfdb254bd0c2819896f26fba8391fb3e89f5796b","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"a515f66a_1851d804","updated":"2025-01-31 08:16:47.000000000","message":"recheck\n\nopenstack.exceptions.ConflictException: Failed to detach VIF f6f5c1a3-8b7b-4c5c-9139-d61d71c17e34 from bare metal node 72f97c15-76cf-45d9-9648-aa8b3b8198e3: Client Error for url: http://192.168.33.2:6385/v1/nodes/72f97c15-76cf-45d9-9648-aa8b3b8198e3/vifs/f6f5c1a3-8b7b-4c5c-9139-d61d71c17e34, Node 72f97c15-76cf-45d9-9648-aa8b3b8198e3 is locked by host np0039726529, please retry after the current operation is completed.","commit_id":"9c6b4477f84b9360eafe88fe26a3dd230b0f7c50"},{"author":{"_account_id":15197,"name":"Pierre Riteau","email":"pierre@stackhpc.com","username":"priteau","status":"StackHPC"},"change_message_id":"74ae7be5e1c7d8476bed73e99896e54d6730cd03","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"5a49e1a1_dbf5171d","updated":"2025-01-31 13:00:17.000000000","message":"recheck kayobe-overcloud-upgrade-rocky9 failed vm test post upgrade","commit_id":"9c6b4477f84b9360eafe88fe26a3dd230b0f7c50"},{"author":{"_account_id":15197,"name":"Pierre Riteau","email":"pierre@stackhpc.com","username":"priteau","status":"StackHPC"},"change_message_id":"c2338c9aec716aa34d3a1b4e2d5673b8d8061f4a","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"e3ed7f5b_10bad221","updated":"2025-01-30 20:02:25.000000000","message":"recheck ntp sync failed","commit_id":"9c6b4477f84b9360eafe88fe26a3dd230b0f7c50"},{"author":{"_account_id":35263,"name":"Matt Crees","email":"mattc@stackhpc.com","username":"mattcrees"},"change_message_id":"77b0712c43d277ea79b38ca3fb6db25c3a16bf7e","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"a3493e7c_40c3fc5f","updated":"2025-01-30 15:50:14.000000000","message":"recheck: galaxy timeout","commit_id":"9c6b4477f84b9360eafe88fe26a3dd230b0f7c50"}],"ansible/roles/ntp/tasks/sync.yml":[{"author":{"_account_id":28048,"name":"Will Szumski","email":"will@stackhpc.com","username":"jovial"},"change_message_id":"ccea903a810ca6d318226247bb18b4eac28a9fd3","unresolved":true,"context_lines":[{"line_number":3,"context_line":"  become: True"},{"line_number":4,"context_line":"  block:"},{"line_number":5,"context_line":"    - name: Configure burst"},{"line_number":6,"context_line":"      command: chronyc \u0027burst 4/4\u0027"},{"line_number":7,"context_line":""},{"line_number":8,"context_line":"    - name: Step the clock"},{"line_number":9,"context_line":"      command: chronyc makestep"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"dbe6d93a_70f0554d","line":6,"updated":"2024-10-23 12:43:26.000000000","message":"I\u0027ve got a recollection that this will effectively modify your running config (i.e you won\u0027t using what is set in chrony.conf anymore). Should we restart chronyc (or maybe there is a way to reload config) after we have done the sync?","commit_id":"9c6b4477f84b9360eafe88fe26a3dd230b0f7c50"},{"author":{"_account_id":14200,"name":"Maksim Malchuk","email":"maksim.malchuk@gmail.com","username":"mmalchuk"},"change_message_id":"565a9028ecd15dea2139f9673a46c29343bedda3","unresolved":true,"context_lines":[{"line_number":10,"context_line":""},{"line_number":11,"context_line":"    - name: Wait before hardware clock synchronisation"},{"line_number":12,"context_line":"      pause:"},{"line_number":13,"context_line":"        seconds: 5"},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"    - name: Force hardware clock synchronisation"},{"line_number":16,"context_line":"      command: hwclock --systohc"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"532cae9f_eb889f63","line":13,"range":{"start_line":13,"start_character":17,"end_line":13,"end_character":18},"updated":"2024-10-08 10:05:26.000000000","message":"maybe use \u0027chronyc\u0027 in loop to check clock is synced instead of wait ?","commit_id":"9c6b4477f84b9360eafe88fe26a3dd230b0f7c50"},{"author":{"_account_id":15197,"name":"Pierre Riteau","email":"pierre@stackhpc.com","username":"priteau","status":"StackHPC"},"change_message_id":"b2e4f310603b4bd22b94bff8475872f4b8fbbe05","unresolved":false,"context_lines":[{"line_number":10,"context_line":""},{"line_number":11,"context_line":"    - name: Wait before hardware clock synchronisation"},{"line_number":12,"context_line":"      pause:"},{"line_number":13,"context_line":"        seconds: 5"},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"    - name: Force hardware clock synchronisation"},{"line_number":16,"context_line":"      command: hwclock --systohc"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"73eec9eb_4a12e374","line":13,"range":{"start_line":13,"start_character":17,"end_line":13,"end_character":18},"in_reply_to":"532cae9f_eb889f63","updated":"2025-02-03 21:03:35.000000000","message":"I replaced the pause by the `chronyc waitsync` command in https://review.opendev.org/c/openstack/kayobe/+/940646.","commit_id":"9c6b4477f84b9360eafe88fe26a3dd230b0f7c50"},{"author":{"_account_id":14200,"name":"Maksim Malchuk","email":"maksim.malchuk@gmail.com","username":"mmalchuk"},"change_message_id":"0623f2218a9bb8b2f1ffcae5fd4add5412a5f5e8","unresolved":false,"context_lines":[{"line_number":10,"context_line":""},{"line_number":11,"context_line":"    - name: Wait before hardware clock synchronisation"},{"line_number":12,"context_line":"      pause:"},{"line_number":13,"context_line":"        seconds: 5"},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"    - name: Force hardware clock synchronisation"},{"line_number":16,"context_line":"      command: hwclock --systohc"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"837a3e0a_f9dcceae","line":13,"range":{"start_line":13,"start_character":17,"end_line":13,"end_character":18},"in_reply_to":"73eec9eb_4a12e374","updated":"2025-02-07 22:28:46.000000000","message":"thanks a lot","commit_id":"9c6b4477f84b9360eafe88fe26a3dd230b0f7c50"},{"author":{"_account_id":28048,"name":"Will Szumski","email":"will@stackhpc.com","username":"jovial"},"change_message_id":"ccea903a810ca6d318226247bb18b4eac28a9fd3","unresolved":true,"context_lines":[{"line_number":13,"context_line":"        seconds: 5"},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"    - name: Force hardware clock synchronisation"},{"line_number":16,"context_line":"      command: hwclock --systohc"},{"line_number":17,"context_line":"  when: ntp_force_sync | bool"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"93a999e1_284dc6ea","line":16,"updated":"2024-10-23 12:43:26.000000000","message":"Got to be careful not to disable 11 minute mode. Quoting the man page:  \n\n       This mode (we’ll call it \"11 minute mode\") is off until something turns\n       it  on.   The  ntp daemon xntpd is one thing that turns it on.  You can\n       turn it off by running anything, including hwclock --hctosys, that sets\n       the System Time the old fashioned way.\n\n       If  your system runs with 11 minute mode on, don’t use hwclock --adjust\n       or hwclock --hctosys.  You’ll just make a mess.  It  is  acceptable  to\n       use a hwclock --hctosys at startup time to get a reasonable System Time\n       until your system is able to set the  System  Time  from  the  external\n       source and start 11 minute mode.\n\nUnsure if chronyc will re-enable it after restart","commit_id":"9c6b4477f84b9360eafe88fe26a3dd230b0f7c50"}]}