)]}'
{"nova/compute/manager.py":[{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"0adfdbcf79ddba01a5f251f67e31c109040ea17c","unresolved":false,"context_lines":[{"line_number":1317,"context_line":""},{"line_number":1318,"context_line":"            for instance in instances:"},{"line_number":1319,"context_line":"                LOG.debug("},{"line_number":1320,"context_line":"                    \"Instance spawn was interrupted before instance_claim, \""},{"line_number":1321,"context_line":"                    \"setting instance to ERROR state\", instance\u003dinstance)"},{"line_number":1322,"context_line":"                self._set_instance_obj_error_state("},{"line_number":1323,"context_line":"                    context, instance, clean_task_state\u003dTrue)"}],"source_content_type":"text/x-python","patch_set":1,"id":"3fa7e38b_f38a481c","line":1320,"updated":"2019-12-19 21:30:34.000000000","message":"In the recent live migration job failure I see this for a server that was scheduling:\n\nhttps://zuul.opendev.org/t/openstack/build/7e992348a91a43a594cf139108ffe999/log/logs/subnode-2/screen-n-cpu.txt.gz#3954\n\nDec 19 14:04:27.625802 ubuntu-xenial-rax-dfw-0013505912 nova-compute[30379]: DEBUG nova.compute.manager [None req-abf255f9-1ec4-434f-82a8-7335f93165e7 None None] [instance: d4a4c429-e802-4f4a-b810-9cb045c37f1b] Instance spawn was interrupted before instance_claim, setting instance to ERROR state {{(pid\u003d30379) _error_out_instances_whose_build_was_interrupted /opt/stack/new/nova/nova/compute/manager.py:1323}}\n\nIt\u0027s showing up after the compute is being restarted, but I\u0027m not sure why the job is restarting things while there is a server that is still building. Maybe something is broken in pike? The compute restart is due to the job re-configuring itself for ceph.","commit_id":"cab396a54094064d2b85ceb7f04004cbd40707b2"}]}