+ 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-19 19:33:41.401 1 INFO nova.utils [None req-99276a6a-7a2f-4dc1-9f9c-ed34fadfb05f - - - - - -] The default thread pool MainProcess.default is initialized
2026-02-19 19:33:41.876 1 INFO nova.utils [None req-99276a6a-7a2f-4dc1-9f9c-ed34fadfb05f - - - - - -] The cell worker thread pool MainProcess.cell_worker is initialized
2026-02-19 19:33:41.900 1 INFO nova.utils [None req-20b47f37-ced7-4a00-ad36-f099aa8ec560 - - - - - -] The cell worker thread pool MainProcess.cell_worker is shutting down
2026-02-19 19:33:42.900 1 INFO nova.utils [None req-20b47f37-ced7-4a00-ad36-f099aa8ec560 - - - - - -] The cell worker thread pool MainProcess.cell_worker is closed
2026-02-19 19:33:42.900 1 INFO nova.utils [None req-20b47f37-ced7-4a00-ad36-f099aa8ec560 - - - - - -] The default thread pool MainProcess.default is shutting down
2026-02-19 19:33:43.498 1 INFO nova.utils [None req-20b47f37-ced7-4a00-ad36-f099aa8ec560 - - - - - -] The default thread pool MainProcess.default is closed
2026-02-19 19:33:43.509 1 WARNING oslo_config.cfg [None req-20b47f37-ced7-4a00-ad36-f099aa8ec560 - - - - - -] 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-19 19:33:43.552 11 INFO nova.service [-] Starting scheduler node (version 32.1.0)
2026-02-19 19:33:43.564 13 INFO nova.service [-] Starting scheduler node (version 32.1.0)
2026-02-19 19:51:58.907 13 WARNING oslo.service.backend._common.loopingcall [-] Function 'nova.servicegroup.drivers.db.DbDriver._report_state' run outlasted interval by 0.23 sec
2026-02-19 20:12:23.073 11 INFO nova.scheduler.manager [None req-bd4dc44d-e7bb-4649-9348-920b2f8d557f 74d8936a2ae744529df5b2aacf5d3d56 8017868430234ad2be7b6f393b8c973d - - 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-19 20:12:26.486 13 INFO nova.scheduler.manager [None req-f5c8239b-ccdf-4733-ad17-fb4e78ef4e5b 7f7b8144a0f640ca8c76007076b05e3c 3a4da935d6054999a6f07988f30a183d - - 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-19 20:12:41.346 11 INFO nova.scheduler.manager [None req-09d26330-6458-4f79-bd54-3af7d4cb9d24 663d0b70eabb44c2883dd9839d0772cc 9e3835244c8f49c58290c23679acce80 - - 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-19 20:12:42.817 13 INFO nova.scheduler.manager [None req-5816f92d-1207-434c-bc13-6737f609cd62 a1ae63f0ec144b64a5b0e8cf89c46805 962a946ff27e417790c74f41c7da364b - - 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-19 20:12:54.177 11 INFO nova.scheduler.manager [None req-ca58442d-9d9a-4f89-8998-441ae1247eeb e033f7a1e49b405a8138f4c77fba659b a82f82965e2a4e1f97bc8dd04e4bcf8c - - 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-19 20:12:58.573 13 INFO nova.scheduler.manager [None req-3fd04103-1e8d-4b54-baca-9b17ba65d740 bb80dc7d181d4660a4faa2f20ce01778 dcfac6ba185e40b2bf5f49bde0d3af2f - - 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-19 20:13:43.433 11 INFO nova.scheduler.manager [None req-f02f8961-d67f-4729-9283-5bebb1e3e501 315035974c9847f6912292aeace121da 346315705bf74911b100feb6a7430b8c - - 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-19 20:13:58.758 13 INFO nova.scheduler.manager [None req-34309639-575c-488c-a00c-20ee977b1f72 4d6531214ed645ec974d39f69003d988 9e5a17947a9a49fa99cefeb42dbd5314 - - 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-19 20:14:09.772 11 INFO nova.scheduler.manager [None req-99f9baa5-30f5-46bc-84b1-24ef4403fdd9 d27d0b511f9d4f9d9cb55ecb7ae31873 3a2ae7f1e6184c43b796890de539bc12 - - 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-19 20:14:34.100 13 INFO nova.scheduler.manager [None req-890550b2-5b96-4014-94b5-ab96aa03a819 8b92967060ce44f08213d304948fcec7 0cd91e3e4a844639ad0f30e37b9f8023 - - 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.