)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":28048,"name":"Will Szumski","email":"will@stackhpc.com","username":"jovial"},"change_message_id":"780f1e778e3ceec56a230aa80357c9604eddddcf","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"6d269d37_3432ebe4","updated":"2024-03-20 10:23:23.000000000","message":"I looked into this and it appears to be caused by:\n\nkayobe overcloud service upgrade -kt rabbitmq --skip-prechecks\n\nin migrate_rabbitmq_queues, which ends up upgrading kolla-ansible:\n\nhttps://github.com/openstack/kayobe/blob/cca6a3f90ee9f0d43edbd8f5010dae4cadb557ae/kayobe/cli/commands.py#L1652\n\nso I think we either need to make this run in the previous_release kayobe environment or I guess we could run the upgrade command with `kolla ansible run` again (although that seems a little bit dirty).","commit_id":"4fea537349b73947c903122e07708417d3891b30"},{"author":{"_account_id":28048,"name":"Will Szumski","email":"will@stackhpc.com","username":"jovial"},"change_message_id":"52c869bfcd9e288e75fd99f46161bc4319136e0f","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"8f8c9970_c66b38ad","updated":"2024-03-18 16:07:49.000000000","message":"Still seems busted: https://zuul.opendev.org/t/openstack/build/12d6a0b1d3e74a98b1c1ec5face16c08/log/primary/ansible/overcloud-upgrade#5638","commit_id":"4fea537349b73947c903122e07708417d3891b30"},{"author":{"_account_id":28048,"name":"Will Szumski","email":"will@stackhpc.com","username":"jovial"},"change_message_id":"8a4e06a965e46c5a905f52931d4092049c331000","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"ef8d5321_7ef05f8b","in_reply_to":"6d269d37_3432ebe4","updated":"2024-03-20 11:08:54.000000000","message":"That didn\u0027t quite make sense. We run upgrade with the old kayobe and its old requirements because we do not call upgrade_kayobe_venv until after migrate queues, but kolla_ansible_source_url/kolla_ansible_source_version is overridden in overrides.yml.j2.","commit_id":"4fea537349b73947c903122e07708417d3891b30"},{"author":{"_account_id":28048,"name":"Will Szumski","email":"will@stackhpc.com","username":"jovial"},"change_message_id":"e9018d6c020694aba119347f5f79a64318be7593","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"250b65a1_7d9fa2b3","updated":"2024-03-20 12:02:49.000000000","message":"I did a quick an dirty solution inspired by kolla-ansible:\n\nhttps://github.com/openstack/kolla-ansible/blob/64575519aa742236fa1ebd493e7f198b7b1d26ba/tests/upgrade.sh#L10-L50\n\nIssue is I don\u0027t think it is testing our documented procedure so we might want to rework it. I don\u0027t think the original method was doing what we thought. I believe we were essentially upgrading the containers via deploy (as we had switched to the current release). What I thought we wanted to do was to migrate to the new default for rabbit queues on the old release.","commit_id":"6c3ff821209a29bd6160602a7ad39aa118708441"},{"author":{"_account_id":28048,"name":"Will Szumski","email":"will@stackhpc.com","username":"jovial"},"change_message_id":"2e953c6f6270eff538e41337ee3287609a7f0c00","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"73b8ff6c_ab3d1444","in_reply_to":"250b65a1_7d9fa2b3","updated":"2024-03-20 12:17:49.000000000","message":"Perhaps if this works we could merge this change to unbreak CI and rework the migrate queues in a different patch? What do people think?","commit_id":"6c3ff821209a29bd6160602a7ad39aa118708441"},{"author":{"_account_id":22629,"name":"Michal Nasiadka","email":"mnasiadka@gmail.com","username":"mnasiadka"},"change_message_id":"ce2328ce67b0f984c9db45badad509cd94545765","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":8,"id":"3ffbab2d_7eb10c09","updated":"2024-04-05 04:45:45.000000000","message":"recheck upgrade-rocky9 post failure","commit_id":"d6bdef9e586d98d7108cc890aefe0cf797fffee1"},{"author":{"_account_id":28048,"name":"Will Szumski","email":"will@stackhpc.com","username":"jovial"},"change_message_id":"553a2558fcc6f3c78b817d716a0966d5613d1fb6","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":8,"id":"4b9cc0c2_bfa59336","updated":"2024-04-04 11:01:03.000000000","message":"recheck: mariadb issues","commit_id":"d6bdef9e586d98d7108cc890aefe0cf797fffee1"}]}