+ 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:31:01.239 1 INFO nova.utils [None req-40c5cdb0-aeb3-488a-8ed8-6db0ef7fc962 - - - - - -] The default thread pool MainProcess.default is initialized
2026-02-26 03:31:01.590 1 INFO nova.utils [None req-40c5cdb0-aeb3-488a-8ed8-6db0ef7fc962 - - - - - -] The cell worker thread pool MainProcess.cell_worker is initialized
2026-02-26 03:31:01.621 1 INFO nova.utils [None req-7c47da8d-3e2e-459b-9b26-98569623ada9 - - - - - -] The cell worker thread pool MainProcess.cell_worker is shutting down
2026-02-26 03:31:02.621 1 INFO nova.utils [None req-7c47da8d-3e2e-459b-9b26-98569623ada9 - - - - - -] The cell worker thread pool MainProcess.cell_worker is closed
2026-02-26 03:31:02.622 1 INFO nova.utils [None req-7c47da8d-3e2e-459b-9b26-98569623ada9 - - - - - -] The default thread pool MainProcess.default is shutting down
2026-02-26 03:31:03.349 1 INFO nova.utils [None req-7c47da8d-3e2e-459b-9b26-98569623ada9 - - - - - -] The default thread pool MainProcess.default is closed
2026-02-26 03:31:03.357 1 WARNING oslo_config.cfg [None req-7c47da8d-3e2e-459b-9b26-98569623ada9 - - - - - -] 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:31:03.401 11 INFO nova.service [-] Starting scheduler node (version 32.1.0)
2026-02-26 03:31:03.417 13 INFO nova.service [-] Starting scheduler node (version 32.1.0)
2026-02-26 03:37:40.742 13 INFO nova.scheduler.host_manager [None req-45b13af8-406a-4feb-bff9-4bd72c72751c - - - - - -] Host mapping not found for host instance. Not tracking instance info for this host.
2026-02-26 03:37:40.742 13 INFO nova.scheduler.host_manager [None req-45b13af8-406a-4feb-bff9-4bd72c72751c - - - - - -] Received a sync request from an unknown host 'instance'. Re-created its InstanceList.
2026-02-26 03:37:40.742 11 INFO nova.scheduler.host_manager [None req-45b13af8-406a-4feb-bff9-4bd72c72751c - - - - - -] Host mapping not found for host instance. Not tracking instance info for this host.
2026-02-26 03:37:40.742 11 INFO nova.scheduler.host_manager [None req-45b13af8-406a-4feb-bff9-4bd72c72751c - - - - - -] Received a sync request from an unknown host 'instance'. Re-created its InstanceList.
2026-02-26 04:07:03.148 11 INFO nova.scheduler.manager [None req-d1b35d2e-0c82-40f1-9fed-d411cec91f0d 6fcd5e02843c4e77942f3395a50ba241 8d75cedd32cf407f9a4cecacb9c9175c - - 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:07:07.469 13 INFO nova.scheduler.manager [None req-c8faa803-f844-4463-b042-39c923f86c85 e0bb4256c37943ae8c5e6d1e80a9b27f abcb998d2e5e42bc849f736d0561d3e0 - - 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:07:21.727 11 INFO nova.scheduler.manager [None req-900e7b75-8d78-46ef-87e8-e76d2d3881e8 8b7cc825ae544c5fa42bc8bf8030a20b 3463c8af9d954c30b2adc3e89236c9d1 - - 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:07:27.598 13 INFO nova.scheduler.manager [None req-6db81275-f72d-4455-bedc-1c96857b891a d87753b0f2174e6cb2f071f96b4014ed 9c558a5ee76c47be9cf73d019596f9eb - - 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:07:38.192 11 INFO nova.scheduler.manager [None req-ab53945c-2d08-4a32-8f24-64cf18fcc25f 0cbf9cdff1db44cf9bc2edff3c15f064 b1fdcf24b1314f438ce350be6edcc715 - - 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:07:55.050 13 INFO nova.scheduler.manager [None req-a43153f6-f786-4a04-8a7b-5bb75892dc89 2a38953a865c44578318430ff9960f0c 789f8df98b63452788fa8a2227d716ff - - 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:56.347 11 INFO nova.scheduler.manager [None req-4646265a-12b7-45bb-a04c-20815aa3d983 333560fdb5e8418fa2868f99b2804f93 d2b51a81c5044a7aa6ab993432f89708 - - 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.561 13 INFO nova.scheduler.manager [None req-f5138087-27e6-458a-a398-136096d7ee57 2b32b66b53c843eea9b64ef33f65b2fc 0a4b121a63f24fc0949ebe72274a8942 - - 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:40.727 11 INFO nova.scheduler.manager [None req-6e66e39e-5bad-41ad-9579-3a8c05e11853 0b8cd95c31994ad7b5a4716c48f34754 d0f62979527a4a6f8a87ddc97dc47f33 - - 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:41.755 13 INFO nova.scheduler.manager [None req-797747ee-e328-461b-814e-d4c5516376a0 69d354f7afc2486c9712a3fa217ce638 e117bc3b248d44b197dc4296b110836f - - 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.