+ exec nova-scheduler --config-file /etc/nova/nova.conf Service is starting with native threading. This is currently experimental. Do not use it in production without first testing it in pre-production. 2026-02-26 03:33:30.420 1 INFO nova.utils [None req-0b78ca50-c7ea-40f0-90fd-7602e2d7705a - - - - - -] The default thread pool MainProcess.default is initialized 2026-02-26 03:33:30.861 1 INFO nova.utils [None req-0b78ca50-c7ea-40f0-90fd-7602e2d7705a - - - - - -] The cell worker thread pool MainProcess.cell_worker is initialized 2026-02-26 03:33:30.899 1 INFO nova.utils [None req-2eeb6a98-85c6-4317-b1e5-99e9be5164a3 - - - - - -] The cell worker thread pool MainProcess.cell_worker is shutting down 2026-02-26 03:33:31.899 1 INFO nova.utils [None req-2eeb6a98-85c6-4317-b1e5-99e9be5164a3 - - - - - -] The cell worker thread pool MainProcess.cell_worker is closed 2026-02-26 03:33:31.900 1 INFO nova.utils [None req-2eeb6a98-85c6-4317-b1e5-99e9be5164a3 - - - - - -] The default thread pool MainProcess.default is shutting down 2026-02-26 03:33:32.529 1 INFO nova.utils [None req-2eeb6a98-85c6-4317-b1e5-99e9be5164a3 - - - - - -] The default thread pool MainProcess.default is closed 2026-02-26 03:33:32.538 1 WARNING oslo_config.cfg [None req-2eeb6a98-85c6-4317-b1e5-99e9be5164a3 - - - - - -] Deprecated: Option "api_servers" from group "glance" is deprecated for removal ( Support for image service configuration via standard keystoneauth1 Adapter options was added in the 17.0.0 Queens release. The api_servers option was retained temporarily to allow consumers time to cut over to a real load balancing solution. ). Its value may be silently ignored in the future. 2026-02-26 03:33:32.589 11 INFO nova.service [-] Starting scheduler node (version 32.1.0) 2026-02-26 03:33:32.599 13 INFO nova.service [-] Starting scheduler node (version 32.1.0) 2026-02-26 03:40:59.457 11 INFO nova.scheduler.host_manager [None req-4886fe2f-9c31-42d3-bf23-3fb63b1af2b7 - - - - - -] Host mapping not found for host instance. Not tracking instance info for this host. 2026-02-26 03:40:59.457 11 INFO nova.scheduler.host_manager [None req-4886fe2f-9c31-42d3-bf23-3fb63b1af2b7 - - - - - -] Received a sync request from an unknown host 'instance'. Re-created its InstanceList. 2026-02-26 03:40:59.459 13 INFO nova.scheduler.host_manager [None req-4886fe2f-9c31-42d3-bf23-3fb63b1af2b7 - - - - - -] Host mapping not found for host instance. Not tracking instance info for this host. 2026-02-26 03:40:59.459 13 INFO nova.scheduler.host_manager [None req-4886fe2f-9c31-42d3-bf23-3fb63b1af2b7 - - - - - -] Received a sync request from an unknown host 'instance'. Re-created its InstanceList. 2026-02-26 04:08:53.745 11 INFO nova.scheduler.manager [None req-65c73fc4-18da-45f6-9de3-654c24ee687d c572cdfc5e764494979dd59940f9816e e08f15612ae744df98842dde10153ef6 - - default default] Got no allocation candidates from the Placement API. This could be due to insufficient resources or a temporary occurrence as compute nodes start up. 2026-02-26 04:08:58.305 13 INFO nova.scheduler.manager [None req-a2f1766f-cc09-482f-b9de-35c18a6d6689 1e802266dd1d48ddb4b3227ea9dc80ea 828e73f68aa14f28941fa5208079232a - - default default] Got no allocation candidates from the Placement API. This could be due to insufficient resources or a temporary occurrence as compute nodes start up. 2026-02-26 04:09:19.912 11 INFO nova.scheduler.manager [None req-aef95561-1519-46c2-9d54-c138462f2f9d f3ac93d87a684d7bb6be385ec26a8e2c 3649db0ed7ee4337b8720af1e460be4f - - default default] Got no allocation candidates from the Placement API. This could be due to insufficient resources or a temporary occurrence as compute nodes start up. 2026-02-26 04:09:37.124 13 INFO nova.scheduler.manager [None req-6b278125-cf4b-4f3b-b8e1-82d1f4275b36 472fcb8b9c1e49908f21267f824b7f8a 054cb6004c0e448da3e62ec2665d703b - - default default] Got no allocation candidates from the Placement API. This could be due to insufficient resources or a temporary occurrence as compute nodes start up. 2026-02-26 04:09:50.632 11 INFO nova.scheduler.manager [None req-fd99373b-5d1d-4bb6-9b89-9e442eadc391 2f43f7f649914d6bb09085958e8de7bf 266fe8f1653a49f69599b4ebf3c6413f - - default default] Got no allocation candidates from the Placement API. This could be due to insufficient resources or a temporary occurrence as compute nodes start up. 2026-02-26 04:10:02.927 13 INFO nova.scheduler.manager [None req-42179401-6ae4-4886-a4a2-2cc1a907cb9e 90b4cb297e774ffdaac67c0d35fd2d51 9c095198ebe74cc99869d5787f159d0e - - default default] Got no allocation candidates from the Placement API. This could be due to insufficient resources or a temporary occurrence as compute nodes start up. 2026-02-26 04:10:11.458 11 INFO nova.scheduler.manager [None req-e3f0415f-67c1-4024-b762-0807357d3588 a2b7ab4c02b54f489c100eccedf62e11 4675070028a944d7bdac731e019b0e96 - - default default] Got no allocation candidates from the Placement API. This could be due to insufficient resources or a temporary occurrence as compute nodes start up. 2026-02-26 04:10:12.439 13 INFO nova.scheduler.manager [None req-f9aac4c7-5af8-4ce7-9bcb-16d3d44fa5c1 0935e2015b414d4da9e1b095d50a592c 694c337e52e94f8eb6e8c6f869da6085 - - default default] Got no allocation candidates from the Placement API. This could be due to insufficient resources or a temporary occurrence as compute nodes start up. 2026-02-26 04:10:12.698 11 INFO nova.scheduler.manager [None req-e904b459-47b0-4e0c-a476-764e92dfa677 3612abb377094de6ab1b8da77d3f2d7d 91076bf1bd7f4079ab61c810ef545b9f - - default default] Got no allocation candidates from the Placement API. This could be due to insufficient resources or a temporary occurrence as compute nodes start up. 2026-02-26 04:11:06.847 13 INFO nova.scheduler.manager [None req-f48b573c-1953-4fe4-b212-4df22f95a195 d0d652eb21c34895833c5e83e585ebcf c8749d94d33a493ab0b465f259601381 - - default default] Got no allocation candidates from the Placement API. This could be due to insufficient resources or a temporary occurrence as compute nodes start up.