ocp升级版本报错,failed to get ocp info: 'NoneType' object is not subscriptable

【 使用环境 】测试环境
OCP
【 使用版本 】4.3.4
【问题描述】白屏升级OCP到连通性测试的时候报错,日志错误信息

2024-12-31 10:13:33,844 INFO dispatch (request_response_log.py:40) [d1e926fc0f5541a3a19eea661713961e] app receive request, method: GET, url: http://10.10.12.140:8680/api/v1/keys/rsa/public, query_params: , body: , from: 192.168.18.187:31749
2024-12-31 10:13:33,845 INFO dispatch (idle_shutdown.py:36) [d1e926fc0f5541a3a19eea661713961e] dispatch request and update last request time
2024-12-31 10:13:33,848 INFO dispatch (request_response_log.py:43) [d1e926fc0f5541a3a19eea661713961e] app send response, code: 200
2024-12-31 10:13:33,912 INFO dispatch (request_response_log.py:40) [b62032a1f0074c5a8de941c54e1e503a] app receive request, method: POST, url: http://10.10.12.140:8680/api/v1/deployment/ocp/agent/ip, query_params: , body: {"host":"10.10.12.140","port":2883,"database":"ocp_meta","user":"root@ocp_meta","password":"kwZXdvXBxBS1v+9CpDoni6cIq602fZxUvA9RCuIYx74BAq0A3dfDIPyPdDr90Bist8ih5WQygvnmD6L76uZLtkb/WKTqoFsRPDgYtrTYAQfKbO1TnTfwxoAF1ZzA2Y2ZTWyoKdFXRXH1EOuHGqrKZEFHQGL+3mpFswXnx1QefaKxgRcjmYa0qVLvo4S8pdr230n++qb2fsFkziUvkOK11P+4Xl5eIa47bk8i0Uvu2/gDSM5IbHWe7zQ3OzMZWGxZst8+YK4JlQy5ZTyAZIIOXmKrnbp8xcoOjQ/ygS20HMsIliNkh1lM/5y2Huxbx7JXYZRJG8oV5lnx7KgCkouZvA==","cluster_name":"myocp"}, from: 192.168.18.187:31749
2024-12-31 10:13:33,912 INFO dispatch (idle_shutdown.py:36) [b62032a1f0074c5a8de941c54e1e503a] dispatch request and update last request time
2024-12-31 10:13:33,920 INFO get_component_agent (service_info_handler.py:303) [b62032a1f0074c5a8de941c54e1e503a] cursor: <tool.Cursor object at 0x7fea7b10ac40>
2024-12-31 10:13:33,966 INFO get_component_agent (service_info_handler.py:306) [b62032a1f0074c5a8de941c54e1e503a] monitor_tenant: None
2024-12-31 10:13:33,966 ERROR get_component_agent (service_info_handler.py:331) [b62032a1f0074c5a8de941c54e1e503a] failed to get ocp info: 'NoneType' object is not subscriptable
2024-12-31 10:13:33,966 ERROR get_component_agent (service_info_handler.py:332) [b62032a1f0074c5a8de941c54e1e503a] Please ensure the use of the meta tenant.
2024-12-31 10:13:33,967 ERROR new_internal_server_error_exception (response_utils.py:53) [b62032a1f0074c5a8de941c54e1e503a] got internal server error exception: Traceback (most recent call last):
  File "service/handler/service_info_handler.py", line 308, in get_component_agent
TypeError: 'NoneType' object is not subscriptable

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "service/api/v1/service_info.py", line 78, in post_metadb_connection
  File "service/handler/service_info_handler.py", line 333, in get_component_agent
Exception: Failed to get ocp info, Please ensure the use of the meta tenant.

2024-12-31 10:13:33,967 ERROR new_internal_server_error_exception (response_utils.py:54) [b62032a1f0074c5a8de941c54e1e503a] Runing Exception: Failed to get ocp info, Please ensure the use of the meta tenant.
2024-12-31 10:13:33,969 INFO dispatch (request_response_log.py:43) [b62032a1f0074c5a8de941c54e1e503a] app send response, code: 500
^CTraceback (most recent call last):
  File "starlette/routing.py", line 674, in lifespan
  File "uvicorn/lifespan/on.py", line 137, in receive
  File "asyncio/queues.py", line 163, in get
asyncio.exceptions.CancelledError

【复现路径】白屏升级OCP到连通性测试的时候报错,日志错误信息
【附件及日志】推荐使用OceanBase敏捷诊断工具obdiag收集诊断信息,详情参见链接(右键跳转查看):

【SOP系列 22 】——故障诊断第一步(自助诊断和诊断信息收集)

【备注】基于 LLM 和开源文档 RAG 的论坛小助手已开放测试,在发帖时输入 [@论坛小助手] 即可召唤小助手,欢迎试用!

麻烦确认下 是升级ocp 还是使用ocp升级ob?什么版本升级到什么版本?

OceanBase通过白屏安装的4.3.4.0版本,OCP是一起安装的,版本是4.2.2

升级OCP,从4.2.2升级到4.3.2

ocp_meta租户手动连接试下 看是否有异常?



两张图片,第一张是通过Navicat连接的,另外一个是升级的

补充一个问题,通过白屏安装的时候,如果选择 OceanBase 及配套工具,勾选了ocp,但是功能好像少很多,而且数据库会使用4.3.4.0,但是如果选择 OceanBase 云平台 的方式安装,数据库只能选择4.2.1.8,不确定跟这个版本会不会有关系,另外通过第二种方式装的OCP功能会齐全很多,包括数据库备份等功能都有。

这里应该是meta_database

这个问题有进展了吗?