+ 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-25 20:22:31.812 1 INFO nova.utils [None req-4336bb82-4161-438f-ba10-e4185cd1469f - - - - - -] The default thread pool MainProcess.default is initialized
2026-02-25 20:22:32.232 1 INFO nova.utils [None req-4336bb82-4161-438f-ba10-e4185cd1469f - - - - - -] The cell worker thread pool MainProcess.cell_worker is initialized
2026-02-25 20:22:32.284 1 INFO nova.utils [None req-07bb6bae-3193-447f-b6d1-21a0b9e79e7f - - - - - -] The cell worker thread pool MainProcess.cell_worker is shutting down
2026-02-25 20:22:33.284 1 INFO nova.utils [None req-07bb6bae-3193-447f-b6d1-21a0b9e79e7f - - - - - -] The cell worker thread pool MainProcess.cell_worker is closed
2026-02-25 20:22:33.285 1 INFO nova.utils [None req-07bb6bae-3193-447f-b6d1-21a0b9e79e7f - - - - - -] The default thread pool MainProcess.default is shutting down
2026-02-25 20:22:33.928 1 INFO nova.utils [None req-07bb6bae-3193-447f-b6d1-21a0b9e79e7f - - - - - -] The default thread pool MainProcess.default is closed
2026-02-25 20:22:33.939 1 WARNING oslo_config.cfg [None req-07bb6bae-3193-447f-b6d1-21a0b9e79e7f - - - - - -] 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-25 20:22:34.007 11 INFO nova.service [-] Starting scheduler node (version 32.1.0)
2026-02-25 20:22:34.018 13 INFO nova.service [-] Starting scheduler node (version 32.1.0)
2026-02-25 20:58:54.725 11 INFO nova.scheduler.manager [None req-986ee098-e6c6-4ded-9373-81a41f10e821 5e034f681e96436db2166a78156b31e6 3817eb1ff25847d692da0d63c71ed0a8 - - 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-25 20:58:54.759 13 INFO nova.scheduler.manager [None req-76171325-c9ab-47e7-a727-28775f4d583d 2dbb72a92771408495deac425dfdfb0f 73f5637f0c8e44a5a441383940f5e993 - - 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-25 20:59:10.859 11 INFO nova.scheduler.manager [None req-18e8351f-e16e-480a-b2b8-375d39afa3bc 5bcc08081b2e46d89e3e08c5a002162f 48993ecc8a69447587b9fa62436bd017 - - 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-25 20:59:22.814 13 INFO nova.scheduler.manager [None req-375cced8-f975-4392-819f-5f5d50e6e419 5cca0ea67d744c4f833889c87619d1b4 b6e5c09f049d4564a97083d4959bfdbf - - 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-25 20:59:23.336 11 INFO nova.scheduler.manager [None req-71af67e1-69f2-4a1a-901a-4cfccdef179d 35dde9ccb7e3438bb2412074c032ef7f 7cb1fd903a354826853cf5ba84474046 - - 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-25 20:59:40.952 13 INFO nova.scheduler.manager [None req-cdcf9700-f9db-4d98-9bb9-dbac37602e76 7baaba624aa54ede9096bbf1be157b3c 8186cab60340469482556bab76cb23a7 - - 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-25 21:00:49.832 11 INFO nova.scheduler.manager [None req-6cb03365-1c7e-430b-b0c5-0ee9a4814182 de465046b8204a72a90bc015cb758650 087690eab44d4e9383cfb66399f29bd9 - - 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-25 21:01:38.996 13 INFO nova.scheduler.manager [None req-268d9e8b-bded-405c-a655-a07f3e1cbced 7e8b1f32f5d84dfa9b1a445522f23aad 0518b5362e534ddab742419fce130555 - - 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-25 21:01:40.116 11 INFO nova.scheduler.manager [None req-a7924e6d-c659-4d0a-a401-13bb948ca902 adf0013c58ce417d8e0434612602c0f1 76a9cd49ef0e4761ae6f7683d10b4e88 - - 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-25 21:01:56.625 13 INFO nova.scheduler.manager [None req-2a6b277b-2838-4f0b-a874-f20156f6a8bf 57442c02d2184c349df56f916f715ae1 7dfec28d3d81485889afc3aa9319324b - - 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.