)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":20813,"name":"Sofia Enriquez","email":"lsofia.enriquez@gmail.com","username":"enriquetaso"},"change_message_id":"a793d223215c4df304d47ef72c25305d2e5a007b","unresolved":true,"context_lines":[{"line_number":12,"context_line":"volumes in the group, it can leave some of the group"},{"line_number":13,"context_line":"volume\u0027s replication status in transient states"},{"line_number":14,"context_line":"(enabling, disabling and failing-over) respectively."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"Closes-Bug: #2003804"},{"line_number":17,"context_line":"Change-Id: Ie94a2b6e5ccfb7c7e6f1999b16409a798715dd13"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"a88aac4b_578a700a","line":15,"updated":"2023-01-25 13:45:16.000000000","message":":-1: Briefly explain why this change fixes the problem.","commit_id":"5e330b979f5a30eafe034aa4971fa404268142fc"},{"author":{"_account_id":24005,"name":"prashkre","email":"prashkre@in.ibm.com","username":"prashkre"},"change_message_id":"9301b71f7f3db60bdb42c2abaef59b97de06eab9","unresolved":false,"context_lines":[{"line_number":12,"context_line":"volumes in the group, it can leave some of the group"},{"line_number":13,"context_line":"volume\u0027s replication status in transient states"},{"line_number":14,"context_line":"(enabling, disabling and failing-over) respectively."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"Closes-Bug: #2003804"},{"line_number":17,"context_line":"Change-Id: Ie94a2b6e5ccfb7c7e6f1999b16409a798715dd13"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"f8442c71_86b88e70","line":15,"in_reply_to":"a88aac4b_578a700a","updated":"2023-06-12 18:28:34.000000000","message":"In this new change-set, replication_status of all volumes is updated only after all volumes in the group meet the pre-conditions such as volume status, volume replication status, group replication status etc. \n\nPreviously before this change-set, we could see that within the same iteration of each volume as soon as pre-conditions are met for a volume, its replication_status is updated and it it not rolled back, if the next volume in the iteration fails to meet any pre-conditions on volume. So this is how the volume\u0027s replication_status are stuck in transient states such as disabling, enabling, failing-over.","commit_id":"5e330b979f5a30eafe034aa4971fa404268142fc"}],"/PATCHSET_LEVEL":[{"author":{"_account_id":20813,"name":"Sofia Enriquez","email":"lsofia.enriquez@gmail.com","username":"enriquetaso"},"change_message_id":"a793d223215c4df304d47ef72c25305d2e5a007b","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"e8dfe8a3_595cfe1d","updated":"2023-01-25 13:45:16.000000000","message":":-1: unittest","commit_id":"5e330b979f5a30eafe034aa4971fa404268142fc"}]}