The rancher log the message bellow irregularly.(Rancher Docker)

2024/01/18 08:12:54 [INFO] [mgmt-auth-crtb-controller] Creating role cluster-owner in namespace p-7gpc5
2024/01/18 08:12:54 [INFO] [mgmt-auth-crtb-controller] Creating role cluster-owner in namespace p-7gpc5
2024/01/18 08:12:54 [INFO] [mgmt-auth-crtb-controller] Creating role cluster-owner in namespace p-7gpc5
2024/01/18 08:12:54 [ERROR] error syncing 'c-m-l68fmb69/u-kiobcohmdl-admin': handler mgmt-auth-crtb-controller: couldn't create role cluster-owner: <http://roles.rbac.authorization.k8s.io|roles.rbac.authorization.k8s.io> "cluster-owner" is forbidden: unable to create new content in namespace p-7gpc5 because it is being terminated, requeuing
2024/01/18 08:12:54 [ERROR] error syncing 'c-m-l68fmb69/creator-cluster-owner': handler mgmt-auth-crtb-controller: couldn't create role cluster-owner: <http://roles.rbac.authorization.k8s.io|roles.rbac.authorization.k8s.io> "cluster-owner" is forbidden: unable to create new content in namespace p-7gpc5 because it is being terminated, requeuing
2024/01/18 08:12:54 [ERROR] error syncing 'c-m-l68fmb69/c-m-l68fmb69-fleet-default-owner': handler mgmt-auth-crtb-controller: couldn't create role cluster-owner: <http://roles.rbac.authorization.k8s.io|roles.rbac.authorization.k8s.io> "cluster-owner" is forbidden: unable to create new content in namespace p-7gpc5 because it is being terminated, requeuing

The rancher repleat the message all the time.(Rancher Docker)

2024/01/18 08:12:56 [INFO] [planner] rkecluster fleet-default/jarvis: waiting: configuring bootstrap node(s) custom-199db9026ce4: waiting for probes: kube-controller-manag
er, kube-scheduler

The rancher-system-agent start by systemctl. There is no more other message.(23.hdp.dc.xyz ROLE: ALL)

Jan 18 15:53:44 23 systemd: Started Rancher System Agent.                                                                    
Jan 18 15:53:44 23 rancher-system-agent: time="2024-01-18T15:53:44+08:00" level=info msg="Rancher System Agent version v0.2.7
 (65aac83) is starting"                                                                                                      
Jan 18 15:53:44 23 rancher-system-agent: time="2024-01-18T15:53:44+08:00" level=info msg="Using directory /var/lib/rancher/ag
ent/work for work"                                                                                                           
Jan 18 15:53:44 23 rancher-system-agent: time="2024-01-18T15:53:44+08:00" level=info msg="Starting remote watch of plans"    
Jan 18 15:53:44 23 rancher-system-agent: time="2024-01-18T15:53:44+08:00" level=info msg="Starting /v1, Kind=Secret controlle
r"

Now. the node 23.hdp.dc.xyz(ROLE: ALL) is stuck .The 24.hdp.dc.xyz(ROLE: ALL) is status as (Waiting for probes: kube-controller-manager, kube-scheduler). How should I do ? I start the Rancher Server by Docker. Thread in Slack Conversation