)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":9816,"name":"Takashi Kajinami","email":"kajinamit@oss.nttdata.com","username":"kajinamit"},"change_message_id":"714e3535b79bda55887d8d49112076d76ef13334","unresolved":true,"context_lines":[{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Remove steps which delete autoscaling stack and do checks"},{"line_number":10,"context_line":"for its deletion. The scenarios are trying to check that"},{"line_number":11,"context_line":"autoscaling works, they don\u0027t need to verify that stack"},{"line_number":12,"context_line":"deletion works - this is a job of the heat-tempest-plugin."},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"Tempest creates a project for each scenario. When the scenario"},{"line_number":15,"context_line":"ends, tempest automatically deletes the project. We previously"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"24190a79_66ed6724","line":12,"range":{"start_line":11,"start_character":45,"end_line":12,"end_character":58},"updated":"2024-05-28 07:54:08.000000000","message":"All tempest tests are supposed to delete the resources created for tests. I agree telemetry-tempest-plugin don\u0027t have to verify the deletion in detail(for example you don\u0027t have to verify deletion of the alarms because it should be deleted by heat) but the plugin should still delete the stack created for CI.","commit_id":"14855245a73ba1dc2027b369eee8de1a2175d989"},{"author":{"_account_id":9816,"name":"Takashi Kajinami","email":"kajinamit@oss.nttdata.com","username":"kajinamit"},"change_message_id":"714e3535b79bda55887d8d49112076d76ef13334","unresolved":true,"context_lines":[{"line_number":12,"context_line":"deletion works - this is a job of the heat-tempest-plugin."},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"Tempest creates a project for each scenario. When the scenario"},{"line_number":15,"context_line":"ends, tempest automatically deletes the project. We previously"},{"line_number":16,"context_line":"had issues with this automatic cleanup, where tempest would"},{"line_number":17,"context_line":"try to delete networks, which still had ports. With this patch"},{"line_number":18,"context_line":"I want to let all the cleanup to tempest and hope, that this"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"78d5b300_4b9f1e68","line":15,"range":{"start_line":15,"start_character":6,"end_line":15,"end_character":47},"updated":"2024-05-28 07:54:08.000000000","message":"it may delete the project but still all resource clean ups should be deleted manually, because there is not single method to purge all resources in a specific project now.","commit_id":"14855245a73ba1dc2027b369eee8de1a2175d989"},{"author":{"_account_id":9816,"name":"Takashi Kajinami","email":"kajinamit@oss.nttdata.com","username":"kajinamit"},"change_message_id":"966e306a8f108c29698419f48c8284039a4caf8e","unresolved":true,"context_lines":[{"line_number":12,"context_line":"deletion works - this is a job of the heat-tempest-plugin."},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"Tempest creates a project for each scenario. When the scenario"},{"line_number":15,"context_line":"ends, tempest automatically deletes the project. We previously"},{"line_number":16,"context_line":"had issues with this automatic cleanup, where tempest would"},{"line_number":17,"context_line":"try to delete networks, which still had ports. With this patch"},{"line_number":18,"context_line":"I want to let all the cleanup to tempest and hope, that this"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"6cbbf4b7_3165f942","line":15,"range":{"start_line":15,"start_character":6,"end_line":15,"end_character":47},"in_reply_to":"78d5b300_4b9f1e68","updated":"2024-05-28 07:54:43.000000000","message":"\u003e all resource clean ups should be deleted manually\nI meant that all resources should be deleted manually/additionally.","commit_id":"14855245a73ba1dc2027b369eee8de1a2175d989"}],"/PATCHSET_LEVEL":[{"author":{"_account_id":34975,"name":"Jaromír Wysoglad","email":"jwysogla@redhat.com","username":"jwysogla"},"change_message_id":"756ea76712532c3c8bd0b2afa58cab975a36bb5d","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"ef89da8b_643b7975","updated":"2024-05-28 08:36:52.000000000","message":"Thanks for taking a look at this Takashi. This was an attempt to get rid of some of the cleanup errors we sometimes see (for example https://zuul.opendev.org/t/openstack/build/9830c2f5345e4cb49aac494590826687/console). But I\u0027m currently unsure if those cleanup failures happen only when there is a previous failure or if they happen even when the rest of the scenario is successful. In the example job run the delete stack step actually wasn\u0027t executed (it failed before it got to that step) and it still failed on the cleanup, so this patch actually wouldn\u0027t do anything. I\u0027ll abandon the change and return to investigate the issue more if I see a failure on otherwise successful job run.","commit_id":"24f2c7b18f4cf98d3cc3bf5f6fb0236564eec22d"}]}