+ 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-05-28 02:41:27.550 1 INFO nova.utils [None req-a7efb619-7041-47f8-9a70-7712e22e4818 - - - - - -] The default thread pool MainProcess.default is initialized
2026-05-28 02:41:27.905 1 INFO nova.utils [None req-a7efb619-7041-47f8-9a70-7712e22e4818 - - - - - -] The cell worker thread pool MainProcess.cell_worker is initialized
2026-05-28 02:41:27.935 1 INFO nova.utils [None req-cc5a7129-8c98-4cce-81eb-d3333985ec52 - - - - - -] The cell worker thread pool MainProcess.cell_worker is shutting down
2026-05-28 02:41:28.935 1 INFO nova.utils [None req-cc5a7129-8c98-4cce-81eb-d3333985ec52 - - - - - -] The cell worker thread pool MainProcess.cell_worker is closed
2026-05-28 02:41:28.935 1 INFO nova.utils [None req-cc5a7129-8c98-4cce-81eb-d3333985ec52 - - - - - -] The default thread pool MainProcess.default is shutting down
2026-05-28 02:41:29.657 1 INFO nova.utils [None req-cc5a7129-8c98-4cce-81eb-d3333985ec52 - - - - - -] The default thread pool MainProcess.default is closed
2026-05-28 02:41:29.664 1 WARNING oslo_config.cfg [None req-cc5a7129-8c98-4cce-81eb-d3333985ec52 - - - - - -] 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-05-28 02:41:29.708 11 INFO nova.service [-] Starting scheduler node (version 32.1.0)
2026-05-28 02:41:29.721 13 INFO nova.service [-] Starting scheduler node (version 32.1.0)
2026-05-28 02:59:04.995 13 WARNING oslo.service.backend._common.loopingcall [-] Function 'nova.servicegroup.drivers.db.DbDriver._report_state' run outlasted interval by 0.23 sec
2026-05-28 02:59:05.001 11 WARNING oslo.service.backend._common.loopingcall [-] Function 'nova.servicegroup.drivers.db.DbDriver._report_state' run outlasted interval by 0.24 sec
2026-05-28 03:21:28.682 13 INFO nova.scheduler.manager [None req-51b6f8e8-e10d-49c7-a270-425c36abaffb a74ca2be360c444890eb1db375775480 dbbae05e2816470aabe18a21df1606da - - 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-05-28 03:21:29.087 11 INFO nova.scheduler.manager [None req-bed05ad9-8b1c-484a-b423-2688825f7bbe fba27c16b8934c48a38fb995713cab2b fa93058550604b93aec949e5f3f26106 - - 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-05-28 03:21:45.880 13 INFO nova.scheduler.manager [None req-93664245-2e75-4a4a-8f03-fab21ff51dd3 6387c84f722442cb963a95dddc3c961f 45c97812a5614774a6de4ed640ac715a - - 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-05-28 03:21:49.155 11 INFO nova.scheduler.manager [None req-63a10b64-3bfe-4381-bc0c-cd79a278858c de8dbcbb067e41b6974e77432c125976 8db80f07ec27428ba17081ddf3c1e29b - - 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-05-28 03:22:03.026 13 INFO nova.scheduler.manager [None req-a1bd5af2-97b0-48cf-9f9b-8092b6281f66 7eb02c9e98584583930d3e450feaf39a 0a613eef6d454a7e966c8d98c95e1062 - - 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-05-28 03:22:09.089 11 INFO nova.scheduler.manager [None req-79037ee3-b264-4acf-a1d0-d30846050ddd b4b6738bf95e412fa01b6fddcfcdfd87 21c7f50db2734c40b22b8b798361608d - - 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-05-28 03:23:34.230 13 INFO nova.scheduler.manager [None req-f08780d7-f9a3-4316-8a24-a7f085b2f087 b266563e8f3449158d42238abd65957c 58eeacad587a4881bfd7ae1a9de49e53 - - 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-05-28 03:24:00.113 11 INFO nova.scheduler.manager [None req-e817db6d-b3a9-4021-8580-2206756f7db5 4665e23023d1468d9d1fdd2e2990017b ee61cebbbe144b329ec5013fb3729d73 - - 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-05-28 03:24:27.598 13 INFO nova.scheduler.manager [None req-04017cfc-41e0-4d13-8c41-a667ba041da2 d1d03cb929554e45b270b09ebb1b684f c08649c6ef654db28697473a97b4639b - - 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-05-28 03:24:42.460 11 INFO nova.scheduler.manager [None req-bdf99b4c-f18f-4fa9-a666-72c7b8b67e9f 75e4e9d2a7f84ec6afb074385735b706 6620a2cb13944c22b7516a8b15b95cde - - 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.