)]}'
{"ironic/conductor/utils.py":[{"author":{"_account_id":12356,"name":"Vladyslav Drok","email":"vdrok@mirantis.com","username":"vdrok"},"change_message_id":"1852b55dcca957fe353f61307c3d478397f829ae","unresolved":false,"context_lines":[{"line_number":227,"context_line":"        task.process_event(\u0027fail\u0027, target_state\u003dtarget_state)"},{"line_number":228,"context_line":""},{"line_number":229,"context_line":""},{"line_number":230,"context_line":"def spawn_cleaning_error_handler(e, node):"},{"line_number":231,"context_line":"    \"\"\"Handle spawning error for node cleaning.\"\"\""},{"line_number":232,"context_line":"    if isinstance(e, exception.NoFreeConductorWorker):"},{"line_number":233,"context_line":"        node.last_error \u003d (_(\"No free conductor workers available\"))"}],"source_content_type":"text/x-python","patch_set":2,"id":"7a5de9d1_348c1235","line":230,"updated":"2016-02-02 13:53:06.000000000","message":"Might be also worth adding a clean step info when this error happened. Or maybe it\u0027s not necessary as it remains in node.clean_step.","commit_id":"0bf63e112b244b51c91fb7da3564fc0d1f94fd29"}],"ironic/drivers/modules/agent_base_vendor.py":[{"author":{"_account_id":13362,"name":"Tan Lin","email":"lin.tan@intel.com","username":"zero"},"change_message_id":"bea9eaa9616e108050c4068b2dd007c04f403c5f","unresolved":false,"context_lines":[{"line_number":360,"context_line":"                    else:"},{"line_number":361,"context_line":"                        msg \u003d _(\u0027Node failed to check cleaning progress.\u0027)"},{"line_number":362,"context_line":"                        self.continue_cleaning(task, **kwargs)"},{"line_number":363,"context_line":"                except exception.NoFreeConductorWorker:"},{"line_number":364,"context_line":"                    # waiting for the next heartbeat, node.last_error and"},{"line_number":365,"context_line":"                    # logging message is filled already via conductor\u0027s hook"},{"line_number":366,"context_line":"                    pass"}],"source_content_type":"text/x-python","patch_set":1,"id":"7a5de9d1_c132eca6","line":363,"updated":"2016-02-01 08:23:45.000000000","message":"nit:this will keep trying for ever?","commit_id":"3e2697aef367507ef91c9ccd993242bc0535aa99"},{"author":{"_account_id":7711,"name":"Yuriy Zveryanskyy","email":"yzveryanskyy@mirantis.com","username":"yuriyz"},"change_message_id":"5c4516d0585a6ab24723a858df80494b839657ce","unresolved":false,"context_lines":[{"line_number":360,"context_line":"                    else:"},{"line_number":361,"context_line":"                        msg \u003d _(\u0027Node failed to check cleaning progress.\u0027)"},{"line_number":362,"context_line":"                        self.continue_cleaning(task, **kwargs)"},{"line_number":363,"context_line":"                except exception.NoFreeConductorWorker:"},{"line_number":364,"context_line":"                    # waiting for the next heartbeat, node.last_error and"},{"line_number":365,"context_line":"                    # logging message is filled already via conductor\u0027s hook"},{"line_number":366,"context_line":"                    pass"}],"source_content_type":"text/x-python","patch_set":1,"id":"7a5de9d1_dc860adb","line":363,"in_reply_to":"7a5de9d1_c132eca6","updated":"2016-02-02 12:59:02.000000000","message":"In normal case this is rare error, if IPA can not obtain a new conductor\u0027s thread for a long time conductor is in non-functional state at all, many other errors will happen.","commit_id":"3e2697aef367507ef91c9ccd993242bc0535aa99"}],"releasenotes/notes/fix-cleaning-spawn-error-60b60281f3be51c2.yaml":[{"author":{"_account_id":12356,"name":"Vladyslav Drok","email":"vdrok@mirantis.com","username":"vdrok"},"change_message_id":"1852b55dcca957fe353f61307c3d478397f829ae","unresolved":false,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"fixes:"},{"line_number":3,"context_line":"  - Fix issues with handle error when spawning a new thread for continue"},{"line_number":4,"context_line":"    cleaning. See https://bugs.launchpad.net/ironic/+bug/1539118."}],"source_content_type":"text/x-yaml","patch_set":2,"id":"7a5de9d1_54fbce47","line":3,"updated":"2016-02-02 13:53:06.000000000","message":"s/handle error/error handling/, s/for continue/to continue/","commit_id":"0bf63e112b244b51c91fb7da3564fc0d1f94fd29"},{"author":{"_account_id":7711,"name":"Yuriy Zveryanskyy","email":"yzveryanskyy@mirantis.com","username":"yuriyz"},"change_message_id":"e98fd9f83cc9a1a5e6ea5dfc0ab51e006c36f410","unresolved":false,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"fixes:"},{"line_number":3,"context_line":"  - Fix issues with handle error when spawning a new thread for continue"},{"line_number":4,"context_line":"    cleaning. See https://bugs.launchpad.net/ironic/+bug/1539118."}],"source_content_type":"text/x-yaml","patch_set":2,"id":"7a5de9d1_1d0499c4","line":3,"in_reply_to":"7a5de9d1_54fbce47","updated":"2016-02-02 14:31:03.000000000","message":"Done","commit_id":"0bf63e112b244b51c91fb7da3564fc0d1f94fd29"}]}
