+ 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:23:38.392 1 INFO nova.utils [None req-49a35501-b235-4f1c-ba3f-bf0e7767791f - - - - - -] The default thread pool MainProcess.default is initialized
2026-02-25 20:23:38.749 1 INFO nova.utils [None req-49a35501-b235-4f1c-ba3f-bf0e7767791f - - - - - -] The cell worker thread pool MainProcess.cell_worker is initialized
2026-02-25 20:23:38.779 1 INFO nova.utils [None req-6bcbd66c-18b5-4daf-9701-dd9d4007bc9c - - - - - -] The cell worker thread pool MainProcess.cell_worker is shutting down
2026-02-25 20:23:39.779 1 INFO nova.utils [None req-6bcbd66c-18b5-4daf-9701-dd9d4007bc9c - - - - - -] The cell worker thread pool MainProcess.cell_worker is closed
2026-02-25 20:23:39.780 1 INFO nova.utils [None req-6bcbd66c-18b5-4daf-9701-dd9d4007bc9c - - - - - -] The default thread pool MainProcess.default is shutting down
2026-02-25 20:23:40.495 1 INFO nova.utils [None req-6bcbd66c-18b5-4daf-9701-dd9d4007bc9c - - - - - -] The default thread pool MainProcess.default is closed
2026-02-25 20:23:40.506 1 WARNING oslo_config.cfg [None req-6bcbd66c-18b5-4daf-9701-dd9d4007bc9c - - - - - -] 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:23:40.554 11 INFO nova.service [-] Starting scheduler node (version 32.1.0)
2026-02-25 20:23:40.568 13 INFO nova.service [-] Starting scheduler node (version 32.1.0)
2026-02-25 20:59:29.831 11 INFO nova.scheduler.manager [None req-7cec165e-1dbc-4727-b1a2-8d469b6c8577 912b055e27fa4bd2a31026d4b30a1176 51a43fc8cda64fbf807d3822ec8bab2c - - 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:31.735 13 INFO nova.scheduler.manager [None req-32c7a33c-aa02-480a-9377-532ec97eb4f9 53b141011cd748ebb33872e7136298d2 10e83aac4dcb4e49a3c613e10a8a1e50 - - 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:39.551 11 INFO nova.scheduler.manager [None req-11a4dade-7c38-40c2-964b-4f3cb625ae47 ebc80a035d1d41078ee4711040f85c27 c5a0a2bf9e814242accb45a8fdd87c9d - - 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:47.601 13 INFO nova.scheduler.manager [None req-c6b6f31c-daec-42c2-a523-b2741dc5dbe9 c2ec79d879894d8e989ae4d20d960577 b4c255232e5146b28577bcacd3ed9b08 - - 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:53.726 11 INFO nova.scheduler.manager [None req-ef9e9387-7f8f-498f-ac3a-2713a6d64287 26175a729b3d433f82a2401f5f6ad9e3 842e830a5dde4193af5d2ee7e5585a9d - - 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:00.195 13 INFO nova.scheduler.manager [None req-372534f2-df9b-44b2-a0fc-d811a38760f6 2c68b072b7b04c1db33d5820925926f8 c9de9896b51f4d76a221926b73c7bafd - - 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:00.587 11 INFO nova.scheduler.manager [None req-48d5bb76-6da6-4e39-896a-4cbbb106f66b 9e93b26a7d7e483eb4edd6cf367723ba 11a547d1db19413ba92b0b6095ee93f7 - - 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:03.331 13 INFO nova.scheduler.manager [None req-4a94da7c-d262-4240-b580-074f6751745b 32776cfcbefd4e5288c1b3e481d206ae 7ace3b2518b24c5b81e2da858690a817 - - 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:24.518 11 INFO nova.scheduler.manager [None req-3e2fca16-0313-427d-bda5-48fbd3f8a6d6 1178fe01140a4346932352089f07cd15 4c1e2294ce074a4abd123912d3316a17 - - 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:44.326 13 INFO nova.scheduler.manager [None req-72828e0b-5c46-42ba-84f7-0df779bc5f69 c8159ff457754ac29d9f77c8dff8d4c7 abfa8495b8784e6c9a3d8bda6a11367d - - 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.