+ exec nova-scheduler --config-file /etc/nova/nova.conf
Modules with known eventlet monkey patching issues were imported prior to eventlet monkey patching: urllib3. This warning can usually be ignored if the caller is only importing and not executing nova code.
/var/lib/openstack/lib/python3.10/site-packages/nova/virt/__init__.py:18: UserWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html. The pkg_resources package is slated for removal as early as 2025-11-30. Refrain from using this package or pin to Setuptools<81.
  __import__('pkg_resources').declare_namespace(__name__)
2026-05-08 18:53:39.493 1 WARNING nova.scheduler.filters.availability_zone_filter [None req-409635fb-9eb1-41ba-b6a6-569dedab62f8 - - - - - -] The 'AvailabilityZoneFilter' is deprecated since the 24.0.0 (Xena) release. Since the 18.0.0 (Rocky) release, nova has supported mapping AZs to placement aggregates. The feature is enabled by the 'query_placement_for_availability_zone' config option and is now enabled by default. As such, the 'AvailabilityZoneFilter' is no longer required. Nova is currently configured to use both placement and the AvailabilityZoneFilter for AZ enforcement.
2026-05-08 18:53:40.023 1 INFO oslo_service.service [None req-1ac2b04e-ddda-48cc-97f0-d9cefe3f1d0f - - - - - -] Starting 2 workers
2026-05-08 18:53:40.033 8 INFO nova.service [-] Starting scheduler node (version 26.3.1)
2026-05-08 18:53:40.034 7 INFO nova.service [-] Starting scheduler node (version 26.3.1)
2026-05-08 18:53:40.038 1 WARNING oslo_config.cfg [None req-1ac2b04e-ddda-48cc-97f0-d9cefe3f1d0f - - - - - -] 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-08 19:30:01.855 7 INFO nova.scheduler.manager [None req-17ccd14c-32bf-4496-945f-5cb261db123c 26a576447d0a4e2e86a9a8ceeef3149d 20d63697dc1443a4818e1f9d22ef4534 - - 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-08 19:30:08.977 8 INFO nova.scheduler.manager [None req-077b341c-c719-47b6-9588-ab13a3c1f855 d8fc10b94e5445aca2c8f610ba24045d 1ecc88d37bbc4f04be07f162641f104e - - 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-08 19:30:17.497 7 INFO nova.scheduler.manager [None req-571a2436-0c44-4c33-8f6c-3727b27e823b 50cdd03d2313463e8f95ed5ac6ed6eaa d23145985e404c09a53ce987678705f6 - - 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-08 19:30:18.681 8 INFO nova.scheduler.manager [None req-23a01a42-d6f1-4522-b625-54a15dda6af3 ea663f6bbdd04d918f7508465cab1131 7d14d0885153441d8d0297f2fbf9c06a - - 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-08 19:30:20.200 7 INFO nova.scheduler.manager [None req-36b05502-e1f0-4b9d-b40b-006866d6fab1 9634612f69c9471281b0b8a68e612ecf 82394a39c1484436b98fc3769c6bc52a - - 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-08 19:30:33.512 8 INFO nova.scheduler.manager [None req-8cf120fc-f0b5-4b0e-861e-67e932b43e30 3fcb6c254a5246dbbf38b1bc5c0b466d a8ca6d707aef4ca48656a5ba992873d3 - - 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-08 19:31:48.182 7 INFO nova.scheduler.manager [None req-f7c2df64-715f-46b8-aa96-32a90ca683cc 476c888368b746068dd7705bbfb5759f 948d654aa123497ab1d6f802bb0c5b15 - - 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-08 19:31:52.301 8 INFO nova.scheduler.manager [None req-385bb61d-58bd-4e28-9664-fa697404edfd b3010e4732b44a96a2bec06ef9989af9 1c6d7c6e0f924057b34394f55c9c75b3 - - 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-08 19:32:14.195 7 INFO nova.scheduler.manager [None req-a011dbdf-eb75-4ce8-b5d2-5ae6448961b9 3f50d7850ba94c0e91b1c2db5c4e331e c8919b9078bf4856a4846dad3e75f700 - - 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-08 19:33:09.787 8 INFO nova.scheduler.manager [None req-06992bc9-6ad9-4955-94b3-dcb821f96cd6 615a2e42287b4593b9ce7fe6f3d00cba fd11ac02a3554dc7a7adc7c95a1c0e40 - - 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.