【 使用环境 】 测试环境
【 OB or 其他组件 】OCP
【 使用版本 】ocp-3.3.0-ce-bp1-x86_64
【问题描述】安装失败
【复现路径】问题出现前后相关操作
【问题现象及影响】
测试使用，为什么一直报内存小于64G,能否规避这个报错安装下去
【附件】
[root@hfocp01 ocp-3.3.0-ce-bp1-x86_64]# ./ocp_installer.sh install -c config_150_single_ocp.yaml -i ./ocp-installer.tar.gz -o ./ocp.tar.gz
install start
check docker on host
load installer docker image
Loaded image: reg.docker.alibaba-inc.com/ocp2/ocp-installer:3.3.0-x86_64
make log dir
make obd dir
2023-02-22 10:39:21 - INFO - 1 - [ob_precheck.py:28] - ob precheck using command: sudo /tmp/precheck-a87ea535-8cf4-4b99-8861-d1365519f144.sh -m ob
2023-02-22 10:39:21 - ERROR - 1 - [ob_precheck.py:32] - precheck for ocp on host 10.251.24.150 failed
2023-02-22 10:39:21 - INFO - 1 - [ob_precheck.py:35] - ob precheck result: Machine Role: ob
Peer IP List:
Machine Type: PHY
Inspect Mode: FALSE
check CPU count: 16 > 8 … PASS
check total MEM: 46 GB < 64 GB … EXPECT >= 64 GB … FAIL
TIPS: replace another machine with more MEM
check linux version: CentOS Linux release 7.9.2009 (Core) … PASS
check SELinux status: Disabled … PASS
check account [admin] and home dir, exist … PASS
check service [firewalld]: inactive … PASS
check service [firewalld]: disabled … PASS
SUMMARY OF ISSUES IN PRE-CHECK
check total MEM: 46 GB < 64 GB … EXPECT >= 64 GB … FAIL
TIPS: replace another machine with more MEM
,
Traceback (most recent call last):
File “install_ocp.py”, line 43, in
run(context)
File “install_ocp.py”, line 33, in run
install_ocp_pipeline.run()
File “/root/installer/pipeline.py”, line 10, in run
task.run()
File “/root/installer/task/ob_precheck.py”, line 38, in run
raise Exception(“ocp precheck failed”)
Exception: ocp precheck failed
config_yaml如下：
OCP deploy config
Note:
Do not use 127.0.0.1 or hostname as server address
When a server has both public ip and private ip, if private ip is connectable, use private ip for faster connection
If a vip is configured, it should be already created and bonded to the right server and port, the installation script won’t do any work with vip maintainance, just use it to connect to the service
Ignore precheck errors
It’s recommanded to not ignore precheck errors
precheck_ignore: false
Create an obcluster as OCP’s metadb
create_metadb_cluster: true
Clean OCP’s metadb cluster when uninstall
clean_metadb_cluster: false
Metadb cluster deploy config
ob_cluster:
name: obcluster
home_path: /home/admin/oceanbase
root_password: ‘sdfG@345’
The directory for data storage, it’s recommanded to use an independent path
data_path: /data/1
The directory for clog, ilog, and slog, it’s recommanded to use an independent path.
redo_path: /data/log1
sql_port: 2881
rpc_port: 2882
zones:
- name: zone1
servers:
- 10.251.24.150
custom obd config for obcluster
custom_config:
- key: devname
value: ens160
Meta user info
meta:
tenant: ocp_meta
user: ocp
password: sdfG@345
database: ocp_meta
cpu: 2
# Memory configs in GB, 4 means 4GB
memory: 4
Monitor user info
monitor:
tenant: ocp_monitor
user: ocp
password: sdfG@345
database: ocp_monitor
cpu: 4
# Memory configs in GB, 8 means 8GB
memory: 8
Obproxy to connect metadb cluster
obproxy:
home_path: /home/admin/obproxy
port: 2883
servers:
- 10.251.24.150
custom config for obproxy
custom_config:
- key: clustername
value: obcluster
Vip is optional, if vip is not configured, one of obproxy servers’s address will be used
vip:
address: 1.1.1.1
port: 2883
Ssh auth config
ssh:
port: 22
user: admin
auth method, support password and pubkey
auth_method: password
timeout: 10
password: Obce@1205
OCP config
ocp:
ocp container’s name
name: ‘ocp’
OCP process listen port and log dir on host
process:
port: 8080
log_dir: /tmp/ocp/log
servers:
- 10.251.24.150
OCP container’s resource
resource:
cpu: 4
# Memory configs in GB, 8 means 8GB
memory: 8
Vip is optional, if vip is not configured, one of ocp servers’s address will be used
vip:
address: 1.1.1.1
port: 8080
OCP basic auth config, used when upgrade ocp
auth:
user: admin
password: sdfG@345
OCP metadb config, for ocp installation, if “create_metadb_cluster” is configured true, this part will be replaced with the configuration of metadb cluster and obproxy
metadb:
host: 10.251.24.150
port: 2883
meta_user: ocp@ocp_meta#obcluster
meta_password: sdfG@345
meta_database: ocp_meta
monitor_user: ocp@ocp_monitor#obcluster
monitor_password: sdfG@345
monitor_database: ocp_monitor