+ exec nova-scheduler --config-file /etc/nova/nova.conf
2026-08-21 03:06:56.812 1 INFO oslo_service.backend.eventlet.service [None req-07610ca2-3257-411e-835d-69317dd74b49 - - - - - -] Starting 2 workers
2026-08-21 03:06:56.821 7 INFO nova.service [-] Starting scheduler node (version 31.3.2)
2026-08-21 03:06:56.825 8 INFO nova.service [-] Starting scheduler node (version 31.3.2)
2026-08-21 03:06:56.826 1 WARNING oslo_config.cfg [None req-07610ca2-3257-411e-835d-69317dd74b49 - - - - - -] 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-08-21 03:46:42.816 8 INFO nova.scheduler.manager [None req-1520785f-f8fa-42b1-b8ba-3043410a08fe b82ef9268a9b4675959ae0635a0d103d bb796b4dc8fd48b896ab19318dee1c75 - - 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-08-21 03:46:42.884 7 INFO nova.scheduler.manager [None req-7457d141-c3af-40e0-a40b-f343feaba84a b42ad9e043b04c30a8017a7f589b4ce0 e1ad094dcfb349d1991e6c86a7f57a68 - - 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-08-21 03:46:59.094 8 INFO nova.scheduler.manager [None req-0c77a8bf-e580-4d2e-a436-103c1525427f 9f3ce2b8faa34915b8b15dc906c472ae 659cf65bda56469181a83ad59b5d4087 - - 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-08-21 03:47:06.598 7 INFO nova.scheduler.manager [None req-72be6e89-d99c-47c7-aae7-a42f48bacf2e 1a858383538f473f9bbb023a0c4f4cf7 a97c13833ea1419a85f7a3537db84b18 - - 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-08-21 03:47:14.486 8 INFO nova.scheduler.manager [None req-7ba247a3-a152-41fd-b74a-4c076a35243e 1d31562165f648189d4be2ab7aea70df 6f9413c609354031b73d7b46f322d39e - - 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-08-21 03:47:29.651 7 INFO nova.scheduler.manager [None req-61abbc3b-e59d-4847-b404-819df9833d6b b9dfb75635e24300ac91dcf474e12775 4c34b732a3b747629295a885668298f3 - - 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-08-21 03:48:30.271 8 INFO nova.scheduler.manager [None req-adc0735c-e8bd-478a-81d2-123c775e979b d159ab4dd0a745e9b48e495209353311 8be8be8884804ebab8a47b883df4d6f2 - - 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-08-21 03:49:07.361 7 INFO nova.scheduler.manager [None req-2f92e328-1126-466c-be57-81057b6d62ba 07219dcd488b4ec89476971d346fd288 e83acf2d5b5e47169ebe5e55762e78d3 - - 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-08-21 03:49:41.601 8 INFO nova.scheduler.manager [None req-c0e63710-6c76-499f-a519-74209450bb2e aa13c3aa229544ac8802d665892a821d fd9bb05c39504489b864f92298c37d61 - - 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-08-21 03:50:11.578 7 INFO nova.scheduler.manager [None req-daf5a463-0456-4710-8b58-8f1e3325b80a b3ced370976340d5aa7ddaac18252259 fd1cd0179a404175b0ce0848c4c406f6 - - 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.