+ 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:25:58 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-6d6756bb4d-b82xp 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 0x7f36d6fa8668 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:26:02.377 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:26:02.395 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:26:02.436 7 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:26:02.547 10 INFO magnum.api.app [-] Full WSGI config used: /etc/magnum/api-paste.ini 2026-03-05 07:26:03.062 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:26:03.067 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 0x7f36d6fa8668 pid: 9 (default app) 2026-03-05 07:26:03.072 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:26:03.077 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 0x7f36d6fa8668 pid: 8 (default app) 2026-03-05 07:26:03.093 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:26:03.097 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 0x7f36d6fa8668 pid: 7 (default app) 2026-03-05 07:26:03.206 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:26:03.211 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 0x7f36d6fa8668 pid: 10 (default app) 2026-03-05 07:26:06.447 9 WARNING oslo_policy.policy [None req-9c41cf38-8fa5-429a-8344-70c8be41da96 - - - - - -] 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:26:06.448 9 WARNING oslo_policy.policy [None req-9c41cf38-8fa5-429a-8344-70c8be41da96 - - - - - -] 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:26:06.459 8 WARNING oslo_policy.policy [None req-e6d3f5b5-f96f-404b-8c3f-10348592de37 - - - - - -] 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:26:06.459 8 WARNING oslo_policy.policy [None req-e6d3f5b5-f96f-404b-8c3f-10348592de37 - - - - - -] 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:26:16.444 7 WARNING oslo_policy.policy [None req-d3ecacb0-db61-40aa-88ab-f2acc851141e - - - - - -] 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:26:16.444 7 WARNING oslo_policy.policy [None req-d3ecacb0-db61-40aa-88ab-f2acc851141e - - - - - -] 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:26:26.448 10 WARNING oslo_policy.policy [None req-73c58d0f-1eee-46b7-8240-9b604e85cb56 - - - - - -] 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:26:26.448 10 WARNING oslo_policy.policy [None req-73c58d0f-1eee-46b7-8240-9b604e85cb56 - - - - - -] 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: 10|app: 0|req: 11/44] 10.0.0.175 () {28 vars in 573 bytes} [Thu Mar 5 07:33:02 2026] GET /v1/clusters => generated 16 bytes in 1430 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 7|app: 0|req: 13/51] 10.0.0.175 () {28 vars in 573 bytes} [Thu Mar 5 07:34:02 2026] GET /v1/clusters => generated 16 bytes in 1110 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.175 () {28 vars in 573 bytes} [Thu Mar 5 07:35:02 2026] GET /v1/clusters => generated 16 bytes in 1207 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.175 () {28 vars in 573 bytes} [Thu Mar 5 07:36:02 2026] GET /v1/clusters => generated 16 bytes in 1288 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 10|app: 0|req: 18/72] 10.0.0.175 () {28 vars in 573 bytes} [Thu Mar 5 07:37:02 2026] GET /v1/clusters => generated 16 bytes in 693 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 7|app: 0|req: 20/79] 10.0.0.175 () {28 vars in 573 bytes} [Thu Mar 5 07:38:02 2026] GET /v1/clusters => generated 16 bytes in 717 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.175 () {28 vars in 573 bytes} [Thu Mar 5 07:39:02 2026] GET /v1/clusters => generated 16 bytes in 674 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.175 () {28 vars in 573 bytes} [Thu Mar 5 07:40:02 2026] GET /v1/clusters => generated 16 bytes in 687 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 10|app: 0|req: 25/100] 10.0.0.175 () {28 vars in 573 bytes} [Thu Mar 5 07:41:02 2026] GET /v1/clusters => generated 16 bytes in 862 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 7|app: 0|req: 27/107] 10.0.0.175 () {28 vars in 573 bytes} [Thu Mar 5 07:42:02 2026] GET /v1/clusters => generated 16 bytes in 723 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.175 () {28 vars in 573 bytes} [Thu Mar 5 07:43:02 2026] GET /v1/clusters => generated 16 bytes in 729 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.175 () {28 vars in 573 bytes} [Thu Mar 5 07:44:02 2026] GET /v1/clusters => generated 16 bytes in 804 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 10|app: 0|req: 32/128] 10.0.0.175 () {28 vars in 573 bytes} [Thu Mar 5 07:45:02 2026] GET /v1/clusters => generated 16 bytes in 737 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 7|app: 0|req: 34/135] 10.0.0.175 () {28 vars in 573 bytes} [Thu Mar 5 07:46:02 2026] GET /v1/clusters => generated 16 bytes in 898 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 8|app: 0|req: 36/142] 10.0.0.175 () {28 vars in 573 bytes} [Thu Mar 5 07:47:02 2026] GET /v1/clusters => generated 16 bytes in 952 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 9|app: 0|req: 38/149] 10.0.0.175 () {28 vars in 573 bytes} [Thu Mar 5 07:48:02 2026] GET /v1/clusters => generated 16 bytes in 1037 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 10|app: 0|req: 39/156] 10.0.0.175 () {28 vars in 573 bytes} [Thu Mar 5 07:49:02 2026] GET /v1/clusters => generated 16 bytes in 935 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 7|app: 0|req: 41/163] 10.0.0.175 () {28 vars in 573 bytes} [Thu Mar 5 07:50:03 2026] GET /v1/clusters => generated 16 bytes in 1131 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 8|app: 0|req: 43/170] 10.0.0.175 () {28 vars in 573 bytes} [Thu Mar 5 07:51:02 2026] GET /v1/clusters => generated 16 bytes in 879 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 9|app: 0|req: 45/177] 10.0.0.175 () {28 vars in 573 bytes} [Thu Mar 5 07:52:02 2026] GET /v1/clusters => generated 16 bytes in 794 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 10|app: 0|req: 46/184] 10.0.0.175 () {28 vars in 573 bytes} [Thu Mar 5 07:53:02 2026] GET /v1/clusters => generated 16 bytes in 870 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 7|app: 0|req: 48/191] 10.0.0.175 () {28 vars in 573 bytes} [Thu Mar 5 07:54:02 2026] GET /v1/clusters => generated 16 bytes in 757 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 8|app: 0|req: 50/198] 10.0.0.175 () {28 vars in 573 bytes} [Thu Mar 5 07:55:02 2026] GET /v1/clusters => generated 16 bytes in 746 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.175 () {28 vars in 573 bytes} [Thu Mar 5 07:56:02 2026] GET /v1/clusters => generated 16 bytes in 886 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 10|app: 0|req: 53/212] 10.0.0.175 () {28 vars in 573 bytes} [Thu Mar 5 07:57:02 2026] GET /v1/clusters => generated 16 bytes in 793 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 7|app: 0|req: 55/219] 10.0.0.175 () {28 vars in 573 bytes} [Thu Mar 5 07:58:02 2026] GET /v1/clusters => generated 16 bytes in 780 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 8|app: 0|req: 57/226] 10.0.0.175 () {28 vars in 573 bytes} [Thu Mar 5 07:59:02 2026] GET /v1/clusters => generated 16 bytes in 721 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0) [pid: 9|app: 0|req: 59/233] 10.0.0.175 () {28 vars in 573 bytes} [Thu Mar 5 08:00:02 2026] GET /v1/clusters => generated 16 bytes in 744 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0)