)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"e1d2557256bff79a98dbad14fd9d2c903c6d5fda","unresolved":false,"context_lines":[{"line_number":16,"context_line":"As an user, previously, If my request is blocked by quota checks, I will"},{"line_number":17,"context_line":"get HTTP 403 response, and no instance records will be left."},{"line_number":18,"context_line":""},{"line_number":19,"context_line":"After the above mentioned change, it is possible that when my requests"},{"line_number":20,"context_line":"failed at conductor layer Quota check and I got an instance in ERROR"},{"line_number":21,"context_line":"state. And in an busy cloud, users may got a lot of ERROR instances"},{"line_number":22,"context_line":"according to this and the instance number may beyond the limit."},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"We should at least mention this behavior change in the release note."},{"line_number":25,"context_line":""}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"7f515b1d_e3835ecb","line":22,"range":{"start_line":19,"start_character":0,"end_line":22,"end_character":63},"updated":"2017-09-26 16:13:45.000000000","message":"So previously, an overquota would _always_ result in no instances (i.e. \u0027openstack server list\u0027 would return now), but now there\u0027s a possibility that instances would be created but would go straight to the ERROR state","commit_id":"c63727799d21e0ea53cd9e5f6e5399cd41a7a0e3"},{"author":{"_account_id":15888,"name":"Zhenyu Zheng","email":"zheng.zhenyu@outlook.com","username":"Kevin_Zheng"},"change_message_id":"24275e66a1ce36918bf62d5e4773c57d90d27e8c","unresolved":false,"context_lines":[{"line_number":16,"context_line":"As an user, previously, If my request is blocked by quota checks, I will"},{"line_number":17,"context_line":"get HTTP 403 response, and no instance records will be left."},{"line_number":18,"context_line":""},{"line_number":19,"context_line":"After the above mentioned change, it is possible that when my requests"},{"line_number":20,"context_line":"failed at conductor layer Quota check and I got an instance in ERROR"},{"line_number":21,"context_line":"state. And in an busy cloud, users may got a lot of ERROR instances"},{"line_number":22,"context_line":"according to this and the instance number may beyond the limit."},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"We should at least mention this behavior change in the release note."},{"line_number":25,"context_line":""}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"7f515b1d_457ea4af","line":22,"range":{"start_line":19,"start_character":0,"end_line":22,"end_character":63},"in_reply_to":"7f515b1d_e3835ecb","updated":"2017-09-27 06:33:39.000000000","message":"Yes","commit_id":"c63727799d21e0ea53cd9e5f6e5399cd41a7a0e3"}],"releasenotes/notes/recheck-quota-conf-043a5d6057b33282.yaml":[{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"e1d2557256bff79a98dbad14fd9d2c903c6d5fda","unresolved":false,"context_lines":[{"line_number":7,"context_line":"    possible for a REST API user to be rejected with an over quota 403 error"},{"line_number":8,"context_line":"    response in the event of a collision close to reaching their quota limit,"},{"line_number":9,"context_line":"    even if the user has enough quota available when they made the request."},{"line_number":10,"context_line":"    And because the quota limit will be recheck serveral times, both in API"},{"line_number":11,"context_line":"    layer and conductor layer, it is possible that requests blocked by over"},{"line_number":12,"context_line":"    quota lead to instances records in ``ERROR`` state. Operators may want"},{"line_number":13,"context_line":"    to set the option to False to avoid additional load on the system if"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"7f515b1d_a3e7a612","line":10,"range":{"start_line":10,"start_character":4,"end_line":10,"end_character":15},"updated":"2017-09-26 16:13:45.000000000","message":"Because","commit_id":"c63727799d21e0ea53cd9e5f6e5399cd41a7a0e3"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"e1d2557256bff79a98dbad14fd9d2c903c6d5fda","unresolved":false,"context_lines":[{"line_number":7,"context_line":"    possible for a REST API user to be rejected with an over quota 403 error"},{"line_number":8,"context_line":"    response in the event of a collision close to reaching their quota limit,"},{"line_number":9,"context_line":"    even if the user has enough quota available when they made the request."},{"line_number":10,"context_line":"    And because the quota limit will be recheck serveral times, both in API"},{"line_number":11,"context_line":"    layer and conductor layer, it is possible that requests blocked by over"},{"line_number":12,"context_line":"    quota lead to instances records in ``ERROR`` state. Operators may want"},{"line_number":13,"context_line":"    to set the option to False to avoid additional load on the system if"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"7f515b1d_83e26a00","line":10,"range":{"start_line":10,"start_character":40,"end_line":10,"end_character":47},"updated":"2017-09-26 16:13:45.000000000","message":"rechecked","commit_id":"c63727799d21e0ea53cd9e5f6e5399cd41a7a0e3"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"e1d2557256bff79a98dbad14fd9d2c903c6d5fda","unresolved":false,"context_lines":[{"line_number":7,"context_line":"    possible for a REST API user to be rejected with an over quota 403 error"},{"line_number":8,"context_line":"    response in the event of a collision close to reaching their quota limit,"},{"line_number":9,"context_line":"    even if the user has enough quota available when they made the request."},{"line_number":10,"context_line":"    And because the quota limit will be recheck serveral times, both in API"},{"line_number":11,"context_line":"    layer and conductor layer, it is possible that requests blocked by over"},{"line_number":12,"context_line":"    quota lead to instances records in ``ERROR`` state. Operators may want"},{"line_number":13,"context_line":"    to set the option to False to avoid additional load on the system if"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"7f515b1d_23d4d61f","line":10,"range":{"start_line":10,"start_character":48,"end_line":10,"end_character":56},"updated":"2017-09-26 16:13:45.000000000","message":"several","commit_id":"c63727799d21e0ea53cd9e5f6e5399cd41a7a0e3"},{"author":{"_account_id":15888,"name":"Zhenyu Zheng","email":"zheng.zhenyu@outlook.com","username":"Kevin_Zheng"},"change_message_id":"24275e66a1ce36918bf62d5e4773c57d90d27e8c","unresolved":false,"context_lines":[{"line_number":7,"context_line":"    possible for a REST API user to be rejected with an over quota 403 error"},{"line_number":8,"context_line":"    response in the event of a collision close to reaching their quota limit,"},{"line_number":9,"context_line":"    even if the user has enough quota available when they made the request."},{"line_number":10,"context_line":"    And because the quota limit will be recheck serveral times, both in API"},{"line_number":11,"context_line":"    layer and conductor layer, it is possible that requests blocked by over"},{"line_number":12,"context_line":"    quota lead to instances records in ``ERROR`` state. Operators may want"},{"line_number":13,"context_line":"    to set the option to False to avoid additional load on the system if"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"7f515b1d_c53854ef","line":10,"range":{"start_line":10,"start_character":4,"end_line":10,"end_character":15},"in_reply_to":"7f515b1d_a3e7a612","updated":"2017-09-27 06:33:39.000000000","message":"Done","commit_id":"c63727799d21e0ea53cd9e5f6e5399cd41a7a0e3"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"e1d2557256bff79a98dbad14fd9d2c903c6d5fda","unresolved":false,"context_lines":[{"line_number":9,"context_line":"    even if the user has enough quota available when they made the request."},{"line_number":10,"context_line":"    And because the quota limit will be recheck serveral times, both in API"},{"line_number":11,"context_line":"    layer and conductor layer, it is possible that requests blocked by over"},{"line_number":12,"context_line":"    quota lead to instances records in ``ERROR`` state. Operators may want"},{"line_number":13,"context_line":"    to set the option to False to avoid additional load on the system if"},{"line_number":14,"context_line":"    allowing quota to be exceeded because of racing requests is considered"},{"line_number":15,"context_line":"    acceptable."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"7f515b1d_43c5925a","line":12,"range":{"start_line":12,"start_character":10,"end_line":12,"end_character":55},"updated":"2017-09-26 16:13:45.000000000","message":"would result in instances in the ``ERROR`` state, rather than no instance records before.","commit_id":"c63727799d21e0ea53cd9e5f6e5399cd41a7a0e3"},{"author":{"_account_id":15888,"name":"Zhenyu Zheng","email":"zheng.zhenyu@outlook.com","username":"Kevin_Zheng"},"change_message_id":"24275e66a1ce36918bf62d5e4773c57d90d27e8c","unresolved":false,"context_lines":[{"line_number":9,"context_line":"    even if the user has enough quota available when they made the request."},{"line_number":10,"context_line":"    And because the quota limit will be recheck serveral times, both in API"},{"line_number":11,"context_line":"    layer and conductor layer, it is possible that requests blocked by over"},{"line_number":12,"context_line":"    quota lead to instances records in ``ERROR`` state. Operators may want"},{"line_number":13,"context_line":"    to set the option to False to avoid additional load on the system if"},{"line_number":14,"context_line":"    allowing quota to be exceeded because of racing requests is considered"},{"line_number":15,"context_line":"    acceptable."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"7f515b1d_e537d0fe","line":12,"range":{"start_line":12,"start_character":10,"end_line":12,"end_character":55},"in_reply_to":"7f515b1d_43c5925a","updated":"2017-09-27 06:33:39.000000000","message":"Done","commit_id":"c63727799d21e0ea53cd9e5f6e5399cd41a7a0e3"}]}