+ COMMAND=start + start + exec uwsgi --ini /etc/magnum/magnum-api-uwsgi.ini [uWSGI] getting INI configuration from /etc/magnum/magnum-api-uwsgi.ini *** Starting uWSGI 2.0.31 (64bit) on [Thu Mar 5 07:28:53 2026] *** compiled with version: 13.3.0 on 30 January 2026 00:34:38 os: Linux-5.15.0-171-generic #181-Ubuntu SMP Fri Feb 6 22:44:50 UTC 2026 nodename: magnum-api-6f78bc676c-7ctv8 machine: x86_64 clock source: unix pcre jit disabled detected number of CPU cores: 16 current working directory: / detected binary path: /var/lib/openstack/bin/uwsgi *** dumping internal routing table *** [rule: 0] subject: user_agent regexp: ^kube-probe.* action: donotlog: *** end of the internal routing table *** your memory page size is 4096 bytes detected max file descriptor number: 1048576 lock engine: pthread robust mutexes thunder lock: enabled uwsgi socket 0 bound to TCP address 0.0.0.0:9511 fd 3 Python version: 3.12.3 (main, Jan 8 2026, 11:30:50) [GCC 13.3.0] Python main interpreter initialized at 0x7f025099c668 python threads support enabled your server socket listen backlog is limited to 100 connections your mercy for graceful operations on workers is 80 seconds mapped 671795 bytes (656 KB) for 4 cores *** Operational MODE: preforking *** *** uWSGI is running in multiple interpreter mode *** spawned uWSGI master process (pid: 1) spawned uWSGI worker 1 (pid: 7, cores: 1) spawned uWSGI worker 2 (pid: 8, cores: 1) spawned uWSGI worker 3 (pid: 9, cores: 1) spawned uWSGI worker 4 (pid: 10, cores: 1) running "unix_signal:15 gracefully_kill_them_all" (master-start)... Using RPC transport for notifications. Please use get_notification_transport to obtain a notification transport instance. 2026-03-05 07:28:57.982 8 INFO magnum.api.app [-] Full WSGI config used: /etc/magnum/api-paste.ini Using RPC transport for notifications. Please use get_notification_transport to obtain a notification transport instance. 2026-03-05 07:28:58.025 9 INFO magnum.api.app [-] Full WSGI config used: /etc/magnum/api-paste.ini Using RPC transport for notifications. Please use get_notification_transport to obtain a notification transport instance. 2026-03-05 07:28:58.086 10 INFO magnum.api.app [-] Full WSGI config used: /etc/magnum/api-paste.ini Using RPC transport for notifications. Please use get_notification_transport to obtain a notification transport instance. 2026-03-05 07:28:58.112 7 INFO magnum.api.app [-] Full WSGI config used: /etc/magnum/api-paste.ini 2026-03-05 07:28:58.679 8 WARNING keystonemiddleware.auth_token [-] AuthToken middleware is set with keystone_authtoken.service_token_roles_required set to False. This is backwards compatible but deprecated behaviour. Please set this to True. 2026-03-05 07:28:58.684 8 WARNING oslo_config.cfg [-] Deprecated: Option "auth_uri" from group "keystone_authtoken" is deprecated. Use option "www_authenticate_uri" from group "keystone_authtoken". WSGI app 0 (mountpoint='') ready in 5 seconds on interpreter 0x7f025099c668 pid: 8 (default app) 2026-03-05 07:28:58.725 9 WARNING keystonemiddleware.auth_token [-] AuthToken middleware is set with keystone_authtoken.service_token_roles_required set to False. This is backwards compatible but deprecated behaviour. Please set this to True. 2026-03-05 07:28:58.730 9 WARNING oslo_config.cfg [-] Deprecated: Option "auth_uri" from group "keystone_authtoken" is deprecated. Use option "www_authenticate_uri" from group "keystone_authtoken". WSGI app 0 (mountpoint='') ready in 5 seconds on interpreter 0x7f025099c668 pid: 9 (default app) 2026-03-05 07:28:58.771 10 WARNING keystonemiddleware.auth_token [-] AuthToken middleware is set with keystone_authtoken.service_token_roles_required set to False. This is backwards compatible but deprecated behaviour. Please set this to True. 2026-03-05 07:28:58.775 10 WARNING oslo_config.cfg [-] Deprecated: Option "auth_uri" from group "keystone_authtoken" is deprecated. Use option "www_authenticate_uri" from group "keystone_authtoken". WSGI app 0 (mountpoint='') ready in 5 seconds on interpreter 0x7f025099c668 pid: 10 (default app) 2026-03-05 07:28:58.792 7 WARNING keystonemiddleware.auth_token [-] AuthToken middleware is set with keystone_authtoken.service_token_roles_required set to False. This is backwards compatible but deprecated behaviour. Please set this to True. 2026-03-05 07:28:58.796 7 WARNING oslo_config.cfg [-] Deprecated: Option "auth_uri" from group "keystone_authtoken" is deprecated. Use option "www_authenticate_uri" from group "keystone_authtoken". WSGI app 0 (mountpoint='') ready in 5 seconds on interpreter 0x7f025099c668 pid: 7 (default app) 2026-03-05 07:29:05.730 8 WARNING oslo_policy.policy [None req-fafe24b6-41ed-4fd9-af4e-ba5dfac0698d - - - - - -] JSON formatted policy_file support is deprecated since Victoria release. You need to use YAML format which will be default in future. You can use ``oslopolicy-convert-json-to-yaml`` tool to convert existing JSON-formatted policy file to YAML-formatted in backward compatible way: https://docs.openstack.org/oslo.policy/latest/cli/oslopolicy-convert-json-to-yaml.html. 2026-03-05 07:29:05.730 8 WARNING oslo_policy.policy [None req-fafe24b6-41ed-4fd9-af4e-ba5dfac0698d - - - - - -] JSON formatted policy_file support is deprecated since Victoria release. You need to use YAML format which will be default in future. You can use ``oslopolicy-convert-json-to-yaml`` tool to convert existing JSON-formatted policy file to YAML-formatted in backward compatible way: https://docs.openstack.org/oslo.policy/latest/cli/oslopolicy-convert-json-to-yaml.html. 2026-03-05 07:29:15.730 9 WARNING oslo_policy.policy [None req-0707598c-a9a6-48b7-990a-5d533038f8d5 - - - - - -] JSON formatted policy_file support is deprecated since Victoria release. You need to use YAML format which will be default in future. You can use ``oslopolicy-convert-json-to-yaml`` tool to convert existing JSON-formatted policy file to YAML-formatted in backward compatible way: https://docs.openstack.org/oslo.policy/latest/cli/oslopolicy-convert-json-to-yaml.html. 2026-03-05 07:29:15.731 9 WARNING oslo_policy.policy [None req-0707598c-a9a6-48b7-990a-5d533038f8d5 - - - - - -] JSON formatted policy_file support is deprecated since Victoria release. You need to use YAML format which will be default in future. You can use ``oslopolicy-convert-json-to-yaml`` tool to convert existing JSON-formatted policy file to YAML-formatted in backward compatible way: https://docs.openstack.org/oslo.policy/latest/cli/oslopolicy-convert-json-to-yaml.html. 2026-03-05 07:29:25.734 10 WARNING oslo_policy.policy [None req-ceeb9f41-edaf-477d-9a89-915a03c80aaf - - - - - -] JSON formatted policy_file support is deprecated since Victoria release. You need to use YAML format which will be default in future. You can use ``oslopolicy-convert-json-to-yaml`` tool to convert existing JSON-formatted policy file to YAML-formatted in backward compatible way: https://docs.openstack.org/oslo.policy/latest/cli/oslopolicy-convert-json-to-yaml.html. 2026-03-05 07:29:25.734 10 WARNING oslo_policy.policy [None req-ceeb9f41-edaf-477d-9a89-915a03c80aaf - - - - - -] JSON formatted policy_file support is deprecated since Victoria release. You need to use YAML format which will be default in future. You can use ``oslopolicy-convert-json-to-yaml`` tool to convert existing JSON-formatted policy file to YAML-formatted in backward compatible way: https://docs.openstack.org/oslo.policy/latest/cli/oslopolicy-convert-json-to-yaml.html. 2026-03-05 07:29:35.732 7 WARNING oslo_policy.policy [None req-54ff2b38-6801-43a4-ab23-ddf9849878ed - - - - - -] JSON formatted policy_file support is deprecated since Victoria release. You need to use YAML format which will be default in future. You can use ``oslopolicy-convert-json-to-yaml`` tool to convert existing JSON-formatted policy file to YAML-formatted in backward compatible way: https://docs.openstack.org/oslo.policy/latest/cli/oslopolicy-convert-json-to-yaml.html. 2026-03-05 07:29:35.733 7 WARNING oslo_policy.policy [None req-54ff2b38-6801-43a4-ab23-ddf9849878ed - - - - - -] JSON formatted policy_file support is deprecated since Victoria release. You need to use YAML format which will be default in future. You can use ``oslopolicy-convert-json-to-yaml`` tool to convert existing JSON-formatted policy file to YAML-formatted in backward compatible way: https://docs.openstack.org/oslo.policy/latest/cli/oslopolicy-convert-json-to-yaml.html. [pid: 8|app: 0|req: 10/38] 10.0.0.182 () {28 vars in 573 bytes} [Thu Mar 5 07:35:04 2026] GET /v1/clusters => generated 16 bytes in 1565 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 7|app: 0|req: 11/44] 10.0.0.182 () {28 vars in 573 bytes} [Thu Mar 5 07:36:04 2026] GET /v1/clusters => generated 16 bytes in 1137 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 10|app: 0|req: 13/51] 10.0.0.182 () {28 vars in 573 bytes} [Thu Mar 5 07:37:04 2026] GET /v1/clusters => generated 16 bytes in 1157 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 8|app: 0|req: 15/58] 10.0.0.182 () {28 vars in 573 bytes} [Thu Mar 5 07:38:04 2026] GET /v1/clusters => generated 16 bytes in 708 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 9|app: 0|req: 17/65] 10.0.0.182 () {28 vars in 573 bytes} [Thu Mar 5 07:39:04 2026] GET /v1/clusters => generated 16 bytes in 1184 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 7|app: 0|req: 18/72] 10.0.0.182 () {28 vars in 573 bytes} [Thu Mar 5 07:40:04 2026] GET /v1/clusters => generated 16 bytes in 825 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 10|app: 0|req: 20/79] 10.0.0.182 () {28 vars in 573 bytes} [Thu Mar 5 07:41:04 2026] GET /v1/clusters => generated 16 bytes in 764 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 8|app: 0|req: 22/86] 10.0.0.182 () {28 vars in 573 bytes} [Thu Mar 5 07:42:04 2026] GET /v1/clusters => generated 16 bytes in 752 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 9|app: 0|req: 24/93] 10.0.0.182 () {28 vars in 573 bytes} [Thu Mar 5 07:43:04 2026] GET /v1/clusters => generated 16 bytes in 871 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 7|app: 0|req: 25/100] 10.0.0.182 () {28 vars in 573 bytes} [Thu Mar 5 07:44:04 2026] GET /v1/clusters => generated 16 bytes in 732 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 10|app: 0|req: 27/107] 10.0.0.182 () {28 vars in 573 bytes} [Thu Mar 5 07:45:04 2026] GET /v1/clusters => generated 16 bytes in 779 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 8|app: 0|req: 29/114] 10.0.0.182 () {28 vars in 573 bytes} [Thu Mar 5 07:46:04 2026] GET /v1/clusters => generated 16 bytes in 787 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 9|app: 0|req: 31/121] 10.0.0.182 () {28 vars in 573 bytes} [Thu Mar 5 07:47:04 2026] GET /v1/clusters => generated 16 bytes in 769 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 7|app: 0|req: 32/128] 10.0.0.182 () {28 vars in 573 bytes} [Thu Mar 5 07:48:04 2026] GET /v1/clusters => generated 16 bytes in 766 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 10|app: 0|req: 34/136] 10.0.0.182 () {28 vars in 573 bytes} [Thu Mar 5 07:49:04 2026] GET /v1/clusters => generated 16 bytes in 1362 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 8|app: 0|req: 36/143] 10.0.0.182 () {28 vars in 573 bytes} [Thu Mar 5 07:50:04 2026] GET /v1/clusters => generated 16 bytes in 1276 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 9|app: 0|req: 38/150] 10.0.0.182 () {28 vars in 573 bytes} [Thu Mar 5 07:51:04 2026] GET /v1/clusters => generated 16 bytes in 1074 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 10|app: 0|req: 39/157] 10.0.0.182 () {28 vars in 573 bytes} [Thu Mar 5 07:52:04 2026] GET /v1/clusters => generated 16 bytes in 1087 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 8|app: 0|req: 41/163] 10.0.0.182 () {28 vars in 573 bytes} [Thu Mar 5 07:53:04 2026] GET /v1/clusters => generated 16 bytes in 1033 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 9|app: 0|req: 43/170] 10.0.0.182 () {28 vars in 573 bytes} [Thu Mar 5 07:54:04 2026] GET /v1/clusters => generated 16 bytes in 920 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 10|app: 0|req: 44/178] 10.0.0.182 () {28 vars in 573 bytes} [Thu Mar 5 07:55:04 2026] GET /v1/clusters => generated 16 bytes in 1045 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 7|app: 0|req: 47/184] 10.0.0.182 () {28 vars in 573 bytes} [Thu Mar 5 07:56:04 2026] GET /v1/clusters => generated 16 bytes in 959 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 8|app: 0|req: 48/191] 10.0.0.182 () {28 vars in 573 bytes} [Thu Mar 5 07:57:04 2026] GET /v1/clusters => generated 16 bytes in 914 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 10|app: 0|req: 49/198] 10.0.0.182 () {28 vars in 573 bytes} [Thu Mar 5 07:58:04 2026] GET /v1/clusters => generated 16 bytes in 786 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 9|app: 0|req: 52/205] 10.0.0.182 () {28 vars in 573 bytes} [Thu Mar 5 07:59:04 2026] GET /v1/clusters => generated 16 bytes in 766 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 7|app: 0|req: 54/212] 10.0.0.182 () {28 vars in 573 bytes} [Thu Mar 5 08:00:04 2026] GET /v1/clusters => generated 16 bytes in 834 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 8|app: 0|req: 55/219] 10.0.0.182 () {28 vars in 573 bytes} [Thu Mar 5 08:01:04 2026] GET /v1/clusters => generated 16 bytes in 775 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0)