+ exec nova-scheduler --config-file /etc/nova/nova.conf
3 RLock(s) were not greened, to fix this error make sure you run eventlet.monkey_patch() before importing any other modules.
2026-05-09 02:08:50.550 1 INFO oslo_service.service [None req-2c72df4d-661d-4213-bbaf-c00e0951c125 - - - - - -] Starting 2 workers
2026-05-09 02:08:50.557 7 INFO nova.service [-] Starting scheduler node (version 30.3.1)
2026-05-09 02:08:50.562 8 INFO nova.service [-] Starting scheduler node (version 30.3.1)
2026-05-09 02:08:50.563 1 WARNING oslo_config.cfg [None req-2c72df4d-661d-4213-bbaf-c00e0951c125 - - - - - -] 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-09 02:42:55.342 7 INFO nova.scheduler.manager [None req-6b859356-d61d-4507-b2d9-d238684fed2f 393f233cd8224c5ba14a28ff8ed9a7fa 35056c5b32e04abc9169f23c28bb7263 - - 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-09 02:42:57.277 8 INFO nova.scheduler.manager [None req-4b862c39-93a8-4318-af41-f875c3a003d6 ba9e73614d594681838325701c5141c6 61caf02448024014b19faad5a2826913 - - 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-09 02:42:57.907 7 INFO nova.scheduler.manager [None req-4a0003d5-cf56-494c-bc2e-d42b29fa6961 309b8ae4e56b4f06aff17bb9983a4c04 b102f2c1d58b49748efcfb7cbd2434d1 - - 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-09 02:43:11.908 8 INFO nova.scheduler.manager [None req-e91538d6-7ddc-4436-a1d0-d16a5d99786b 191894630df643ada1a5ea20c79557a2 72d6a180059b4d78b6469b011c683c8a - - 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-09 02:43:12.482 7 INFO nova.scheduler.manager [None req-2845cb2d-1aca-4a8d-8679-6cdaac83ba07 fab4d328c8cc4efbad310cbdec5f2ba2 3da72143f903428896c0d09c44bc72e3 - - 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-09 02:43:25.439 8 INFO nova.scheduler.manager [None req-80fbda8e-1a83-427b-b072-d8c89ac740b2 672b759fcc164d6babbad250a1bb6221 2b5e0c15726c4bc6b4a31a6bf0669540 - - 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-09 02:44:00.238 7 INFO nova.scheduler.manager [None req-2663d476-213d-4bc2-841e-33bb59b1f884 5478bac2d4574ece9c6956e3f4cea66a def252070b5546dc8fa143ce1eae01e6 - - 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-09 02:44:22.111 8 INFO nova.scheduler.manager [None req-c41ee839-bc94-4d05-9ba4-fa6317c06f6d 1486a3fc9f7f4860b9b7fe3fd168aeb1 47145ab5bc0e440fa71496feffee5634 - - 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-09 02:44:27.440 7 INFO nova.scheduler.manager [None req-e2188805-9876-4726-940c-eb79295396e7 fc008b7848ee4cffac015e8f5894e82f 52e2a634473f491f82710130522ecc6f - - 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-09 02:46:04.518 8 INFO nova.scheduler.manager [None req-27511394-823e-49c3-bcc4-4ba943d87171 5264fb2a866d4c999fcc09ea3d8e7783 aad4eaa74034441e8173dfdc29be62f7 - - 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.