Here is what I encountered on queens during network partition (edited for easier read): nova-compute bmt01 17:17:40,099.099 Final resource view: name=597d7aac-10c3-498b-8311-a3a802feb8ac 17:17:40,337.337 Final resource view: name=a689ac47-8cdb-4162-ab74-5b94f2b22144 17:17:40,526.526 Final resource view: name=feb38a0f-5299-423c-8f46-78ee120f14ee 17:18:58,783.783 compute can not report its status to conductor in nova.servicegroup.drivers.db (on object.Service.save, pymysql.err.InternalError) 17:19:07,437.437 compute fails to perform periodic update_available_resource (on objects.ComputeNode._db_compute_node_get_all_by_host, pymysql.err.InternalError) 17:19:37,444.444 compute fails to perform periodic _sync_scheduler_instance_info (MessagingTimeout in conductor RPCAPI object_class_action_versions) 17:19:45,638.638 No compute node record for bmt01:3baefd99-dbd6-40e3-88a4-dadff5ca4bb8 17:19:45,865.865 ComputeNode 3baefd99-dbd6-40e3-88a4-dadff5ca4bb8 moving from bmt03 to bmt01 17:19:51,450.450 No compute node record for bmt01:1ddc0947-541c-47e5-a77a-3dab82205c21 17:19:51,488.488 ComputeNode 1ddc0947-541c-47e5-a77a-3dab82205c21 moving from bmt03 to bmt01 17:19:57,374.374 No compute node record for bmt01:25934ddf-808f-4bb9-b0f9-55a3e3184cb3 17:19:57,491.491 ComputeNode 25934ddf-808f-4bb9-b0f9-55a3e3184cb3 moving from bmt03 to bmt01 17:19:59,425.425 nova.servicegroup.drivers.db Recovered from being unable to report status. 17:20:01,313.313 No compute node record for bmt01:cf9dd25d-0db0-410b-a91d-58b226126f01 17:20:01,568.568 ComputeNode cf9dd25d-0db0-410b-a91d-58b226126f01 moving from bmt03 to bmt01 17:20:03,513.513 No compute node record for bmt01:812fb0ba-2415-4303-a32f-1dcd6ae591d5 17:20:03,599.599 ComputeNode 812fb0ba-2415-4303-a32f-1dcd6ae591d5 moving from bmt02 to bmt01 17:20:04,717.717 No compute node record for bmt01:db58f55e-1a60-4d20-9eea-5354e2c87bc4 17:20:04,756.756 ComputeNode db58f55e-1a60-4d20-9eea-5354e2c87bc4 moving from bmt03 to bmt01 17:20:06,005.005 No compute node record for bmt01:75ae6252-74e1-4d94-b379-8b1fd3665c57 17:20:06,046.046 ComputeNode 75ae6252-74e1-4d94-b379-8b1fd3665c57 moving from bmt02 to bmt01 17:20:07,153.153 No compute node record for bmt01:787f2ff1-6146-4f6f-aba8-5b37bdb23b25 17:20:07,188.188 ComputeNode 787f2ff1-6146-4f6f-aba8-5b37bdb23b25 moving from bmt03 to bmt01 17:20:08,171.171 No compute node record for bmt01:79c76025-da4f-43ac-a544-0eb5bac76bd8 17:20:08,209.209 ComputeNode 79c76025-da4f-43ac-a544-0eb5bac76bd8 moving from bmt02 to bmt01 17:20:09,178.178 No compute node record for bmt01:ffb3dd3b-f8f9-448f-9cb0-e1e22b996f5e 17:20:09,226.226 ComputeNode ffb3dd3b-f8f9-448f-9cb0-e1e22b996f5e moving from bmt02 to bmt01 17:20:10,411.411 No compute node record for bmt01:50aec742-41fc-46eb-9cf6-6e908ee5040b 17:20:10,428.428 ComputeNode 50aec742-41fc-46eb-9cf6-6e908ee5040b moving from bmt02 to bmt01 17:20:12,168.168 No compute node record for bmt01:83de1b40-5db6-4ecf-9c18-1a83356890ae 17:20:12,195.195 ComputeNode 83de1b40-5db6-4ecf-9c18-1a83356890ae moving from bmt03 to bmt01 ... 17:20:48,502.502 Final resource view: name=597d7aac-10c3-498b-8311-a3a802feb8ac 17:20:48,677.677 Final resource view: name=a689ac47-8cdb-4162-ab74-5b94f2b22144 17:20:48,863.863 Final resource view: name=feb38a0f-5299-423c-8f46-78ee120f14ee 17:20:48,909.909 Deleting orphan compute node 85 hypervisor host is 25934ddf-808f-4bb9-b0f9-55a3e3184cb3, nodes are set(<3 from right above>) 17:20:50,659.659 Deleted resource provider 9f5fac16-2fbf-439b-b355-dcd77df54627 # Resource providers were created by respective compute nodes long ago 17:20:50,660.660 Deleting orphan compute node 91 hypervisor host is 1ddc0947-541c-47e5-a77a-3dab82205c21, 17:20:51,656.656 Deleted resource provider fa3c90a3-b9f1-41ff-b29d-41e55a42fb12 17:20:51,657.657 Deleting orphan compute node 94 hypervisor host is 3baefd99-dbd6-40e3-88a4-dadff5ca4bb8, 17:20:52,777.777 Deleted resource provider fcb784f7-b7e3-468c-b444-0e41cb434248 17:20:52,778.778 Deleting orphan compute node 109 hypervisor host is db58f55e-1a60-4d20-9eea-5354e2c87bc4, 17:20:54,109.109 Deleted resource provider 01e4efa1-b6c7-4597-8fc6-d70255014255 17:20:54,110.110 Deleting orphan compute node 112 hypervisor host is 787f2ff1-6146-4f6f-aba8-5b37bdb23b25, 17:20:54,820.820 Deleted resource provider d6965ae8-1fa7-413d-80d2-4fe063680048 17:20:54,821.821 Deleting orphan compute node 115 hypervisor host is 50aec742-41fc-46eb-9cf6-6e908ee5040b, 17:20:56,698.698 Deleted resource provider e8d0e304-3768-4c52-bdc9-8b780c781dec 17:20:56,699.699 Deleting orphan compute node 118 hypervisor host is ffb3dd3b-f8f9-448f-9cb0-e1e22b996f5e, 17:20:58,180.180 Deleted resource provider 59a7890f-808d-4364-9cc1-8ebd42b713c1 17:20:58,181.181 Deleting orphan compute node 121 hypervisor host is 79c76025-da4f-43ac-a544-0eb5bac76bd8, 17:20:59,653.653 Deleted resource provider ef59a852-68c8-450b-8c33-e36b614a5807 17:20:59,654.654 Deleting orphan compute node 124 hypervisor host is 75ae6252-74e1-4d94-b379-8b1fd3665c57, 17:20:59,877.877 Deleted resource provider d0f16686-3796-45e4-afd0-f29664fa653e 17:20:59,878.878 Deleting orphan compute node 127 hypervisor host is 83de1b40-5db6-4ecf-9c18-1a83356890ae, 17:21:01,113.113 Deleted resource provider c75508d1-c5d8-4185-896c-a0092cd02224 17:21:01,114.114 Deleting orphan compute node 133 hypervisor host is 812fb0ba-2415-4303-a32f-1dcd6ae591d5, 17:21:01,600.600 Deleted resource provider 374158d1-16b1-4f73-98e5-fa49e68ed660 17:21:01,601.601 Deleting orphan compute node 139 hypervisor host is cf9dd25d-0db0-410b-a91d-58b226126f01, 17:21:02,937.937 Deleted resource provider 02b0dae5-dd76-4f4d-9dc7-7ae624213806 17:22:43,108.108 Failed to retrieve aggregates from placement API for resource provider with UUID 740def25-d1eb-49bc-b462-c675632fba1f. Got 404 nova-compute bmt02 17:18:16,345.345 Final resource view: name=79c76025-da4f-43ac-a544-0eb5bac76bd8 17:18:16,606.606 Final resource view: name=812fb0ba-2415-4303-a32f-1dcd6ae591d5 17:18:16,828.828 Final resource view: name=5b9c6cea-eaaf-4b1e-873d-bafa335ae166 17:18:16,977.977 Final resource view: name=75ae6252-74e1-4d94-b379-8b1fd3665c57 17:18:17,113.113 Final resource view: name=ffb3dd3b-f8f9-448f-9cb0-e1e22b996f5e 17:18:17,274.274 Final resource view: name=50aec742-41fc-46eb-9cf6-6e908ee5040b 17:19:01,673.673 A recoverable connection/channel error occurred, trying to reconnect 17:19:18,144.144 AMQP server 172.17.106.41:5672 closed the connection. 17:19:19,168.168 Reconnected to AMQP server on 172.17.106.41:5672 17:19:19,318.318 nova.servicegroup.drivers.db Lost connection to nova-conductor for reporting service status.: MessagingTimeout 17:19:24,715.715 AMQP server on 172.17.106.43:5672 is unreachable 17:19:26,280.280 Error during ComputeManager._heal_instance_info_cache: MessagingTimeout 17:19:26,825.825 Reconnected to AMQP server on 172.17.106.41:5672 17:19:33,000.000 AMQP server on 172.17.106.42:5672 is unreachable 17:19:34,014.014 Reconnected to AMQP server on 172.17.106.42:5672 17:19:41,356.356 A recoverable connection/channel error occurred, trying to reconnect 17:19:41,707.707 Unexpected error during heartbeat thread processing, retrying... 17:19:49,772.772 No compute node record for bmt02:597d7aac-10c3-498b-8311-a3a802feb8ac 17:19:49,814.814 ComputeNode 597d7aac-10c3-498b-8311-a3a802feb8ac moving from bmt01 to bmt02 17:19:50,505.505 nova.servicegroup.drivers.db Recovered from being unable to report status. ... 17:21:19,113.113 Deleting orphan compute node 88 hypervisor host is 597d7aac-10c3-498b-8311-a3a802feb8ac, 17:21:19,431.431 Deleted resource provider 740def25-d1eb-49bc-b462-c675632fba1f # Resource providers were created by respective compute nodes long ago 17:23:20,417.417 Failed to retrieve aggregates from placement API for resource provider with UUID ef59a852-68c8-450b-8c33-e36b614a5807. Got 404 nova-compute bmt03 17:17:50,177.177 Final resource view: name=3baefd99-dbd6-40e3-88a4-dadff5ca4bb8 17:17:50,359.359 Final resource view: name=1ddc0947-541c-47e5-a77a-3dab82205c21 17:17:50,532.532 Final resource view: name=25934ddf-808f-4bb9-b0f9-55a3e3184cb3 17:17:50,657.657 Final resource view: name=cf9dd25d-0db0-410b-a91d-58b226126f01 17:17:50,792.792 Final resource view: name=db58f55e-1a60-4d20-9eea-5354e2c87bc4 17:17:50,938.938 Final resource view: name=787f2ff1-6146-4f6f-aba8-5b37bdb23b25 17:17:51,084.084 Final resource view: name=83de1b40-5db6-4ecf-9c18-1a83356890ae 17:19:00,797.797 AMQP server on 172.17.106.41:5672 is unreachable 17:19:06,807.807 AMQP server on 172.17.106.41:5672 is unreachable 17:19:13,340.340 AMQP server 172.17.106.42:5672 closed the connection. 17:19:14,138.138 Reconnected to AMQP server on 172.17.106.42:5672 17:19:14,361.361 Reconnected to AMQP server on 172.17.106.42:5672 17:19:26,908.908 AMQP server 172.17.106.41:5672 closed the connection. 17:19:27,926.926 Reconnected to AMQP server on 172.17.106.41:5672 17:19:29,497.497 AMQP server on 172.17.106.42:5672 is unreachable 17:19:30,521.521 Reconnected to AMQP server on 172.17.106.42:5672 17:19:30,535.535 A recoverable connection/channel error occurred, trying to reconnect 17:19:31,201.201 Unexpected error during heartbeat thread processing, retrying... 17:19:32,557.557 Unexpected error during heartbeat thread processing, retrying... 17:19:44,364.364 nova.servicegroup.drivers.db Lost connection to nova-conductor for reporting service status.: MessagingTimeout 17:19:46,198.198 Error during ComputeManager.update_available_resource: MessagingTimeout (object_class_action_versions) 17:19:46,216.216 AMQP server on 172.17.106.42:5672 is unreachable 17:19:47,231.231 Reconnected to AMQP server on 172.17.106.42:5672 ... 17:20:07,332.332 nova.servicegroup.drivers.db Recovered from being unable to report status. 17:20:53,372.372 No compute node record for host bmt03: ComputeHostNotFound_Remote: Compute host bmt03 could not be found. # no compute node, only host ... 17:22:57,808.808 Failed to retrieve aggregates from placement API for resource provider with UUID fcb784f7-b7e3-468c-b444-0e41cb434248. Got 404