+ 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 05:51:56 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-77596b5d6b-qm9x6
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 0x7f7b95d8c668
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 05:52:01.309 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 05:52:01.403 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 05:52:01.429 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 05:52:01.477 8 INFO magnum.api.app [-] Full WSGI config used: /etc/magnum/api-paste.ini
2026-03-05 05:52:02.026 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 05:52:02.031 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 6 seconds on interpreter 0x7f7b95d8c668 pid: 10 (default app)
2026-03-05 05:52:02.249 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 05:52:02.255 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 6 seconds on interpreter 0x7f7b95d8c668 pid: 8 (default app)
2026-03-05 05:52:02.279 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 05:52:02.284 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 6 seconds on interpreter 0x7f7b95d8c668 pid: 9 (default app)
2026-03-05 05:52:02.290 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 05:52:02.295 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 6 seconds on interpreter 0x7f7b95d8c668 pid: 7 (default app)
2026-03-05 05:52:09.427 10 WARNING oslo_policy.policy [None req-313186db-c57b-4e7d-be19-cace8252b6f8 - - - - - -] 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 05:52:09.427 10 WARNING oslo_policy.policy [None req-313186db-c57b-4e7d-be19-cace8252b6f8 - - - - - -] 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 05:52:19.427 8 WARNING oslo_policy.policy [None req-8f83d071-ba6d-40e3-9452-facff6bf5de2 - - - - - -] 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 05:52:19.428 8 WARNING oslo_policy.policy [None req-8f83d071-ba6d-40e3-9452-facff6bf5de2 - - - - - -] 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 05:52:29.430 9 WARNING oslo_policy.policy [None req-2b9c4cb8-6d0f-42f4-9486-b12120861b0b - - - - - -] 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 05:52:29.431 9 WARNING oslo_policy.policy [None req-2b9c4cb8-6d0f-42f4-9486-b12120861b0b - - - - - -] 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 05:52:39.425 7 WARNING oslo_policy.policy [None req-e09b6d0b-ad2d-40ad-9cae-b5ac7c21f419 - - - - - -] 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 05:52:39.425 7 WARNING oslo_policy.policy [None req-e09b6d0b-ad2d-40ad-9cae-b5ac7c21f419 - - - - - -] 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: 7|app: 0|req: 14/56] 10.0.0.49 () {28 vars in 572 bytes} [Thu Mar  5 06:01:14 2026] GET /v1/clusters => generated 16 bytes in 1415 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0)
[pid: 9|app: 0|req: 16/63] 10.0.0.49 () {28 vars in 572 bytes} [Thu Mar  5 06:02:14 2026] GET /v1/clusters => generated 16 bytes in 1216 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0)
[pid: 8|app: 0|req: 18/70] 10.0.0.49 () {28 vars in 572 bytes} [Thu Mar  5 06:03:14 2026] GET /v1/clusters => generated 16 bytes in 1217 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0)
[pid: 10|app: 0|req: 20/77] 10.0.0.49 () {28 vars in 572 bytes} [Thu Mar  5 06:04:14 2026] GET /v1/clusters => generated 16 bytes in 1285 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0)
[pid: 7|app: 0|req: 21/84] 10.0.0.49 () {28 vars in 572 bytes} [Thu Mar  5 06:05:14 2026] GET /v1/clusters => generated 16 bytes in 778 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0)
[pid: 9|app: 0|req: 23/91] 10.0.0.49 () {28 vars in 572 bytes} [Thu Mar  5 06:06:14 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: 8|app: 0|req: 25/98] 10.0.0.49 () {28 vars in 572 bytes} [Thu Mar  5 06:07:14 2026] GET /v1/clusters => generated 16 bytes in 861 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0)
[pid: 10|app: 0|req: 27/105] 10.0.0.49 () {28 vars in 572 bytes} [Thu Mar  5 06:08:14 2026] GET /v1/clusters => generated 16 bytes in 826 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0)
[pid: 7|app: 0|req: 28/112] 10.0.0.49 () {28 vars in 572 bytes} [Thu Mar  5 06:09:14 2026] GET /v1/clusters => generated 16 bytes in 772 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0)
[pid: 9|app: 0|req: 30/119] 10.0.0.49 () {28 vars in 572 bytes} [Thu Mar  5 06:10:14 2026] GET /v1/clusters => generated 16 bytes in 810 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0)
[pid: 8|app: 0|req: 32/126] 10.0.0.49 () {28 vars in 572 bytes} [Thu Mar  5 06:11:14 2026] GET /v1/clusters => generated 16 bytes in 768 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0)
[pid: 10|app: 0|req: 34/133] 10.0.0.49 () {28 vars in 572 bytes} [Thu Mar  5 06:12:14 2026] GET /v1/clusters => generated 16 bytes in 962 msecs (HTTP/1.1 200) 8 headers in 334 bytes (1 switches on core 0)