)]}'
{"nova/compute/manager.py":[{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"9c4290006aeb56828928b35b6a5fb9f02e28502f","unresolved":false,"context_lines":[{"line_number":1252,"context_line":"        the service up by listening on RPC queues, make sure to update"},{"line_number":1253,"context_line":"        our available resources (and indirectly our available nodes)."},{"line_number":1254,"context_line":"        \"\"\""},{"line_number":1255,"context_line":"        self.update_available_resource(nova.context.get_admin_context(),"},{"line_number":1256,"context_line":"                                       startup\u003dTrue)"},{"line_number":1257,"context_line":""},{"line_number":1258,"context_line":"    def post_start_hook(self):"}],"source_content_type":"text/x-python","patch_set":3,"id":"3f79a3b5_06c3513a","line":1255,"range":{"start_line":1255,"start_character":13,"end_line":1255,"end_character":38},"updated":"2018-08-29 13:23:05.000000000","message":"This has to hit conductor for several things, like querying the compute_nodes, instances and migrations table. So if we are intermittently timing out trying to hit conductor on init just to query the services table, this change likely just moves the failure to here, which doesn\u0027t really help us.\n\nProbably need some more investigation into why conductor isn\u0027t ready by the time it says it\u0027s active.","commit_id":"e83ffc9dfe17c944a961f33d52a6c59e04c08e5a"}]}