You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
mysqlorc02 and orcproxy02 are both always in Creating status and no pod is created
mysql with topology: semisync cluster mysql2 is running well
orchestrator cluster orchc2 is running well
k get cluster -A
NAMESPACE NAME CLUSTER-DEFINITION TERMINATION-POLICY STATUS AGE
default mysql2 mysql Delete Running 7m44s
default mysqlorc02 mysql Delete Creating 7m58s
default mysqlsp02 mysql Delete Creating 66m
default orchc2 orchestrator Delete Running 2m11s
default orcproxy02 mysql Delete Creating 9m23s
Check cmp
The cmps have no status
k get cmp
NAME DEFINITION SERVICE-VERSION STATUS AGE
mysqlorc02-mysql mysql-orc-8.0-1.0.0-alpha.0 8.0.39 22m
orcproxy02-mysql mysql-orc-8.0-1.0.0-alpha.0 8.0.39 24m
k describe cmp orcproxy02-mysql
Status:
Conditions:
Last Transition Time: 2025-01-17T10:22:31Z
Message: The operator has started the provisioning of Cluster: orcproxy02-mysql
Observed Generation: 1
Reason: PreCheckSucceed
Status: True
Type: ProvisioningStarted
Events: <none>
Describe the env
Kubernetes: v1.31.1-aliyun.1
KubeBlocks: 1.0.0-beta.23
kbcli: 1.0.0-beta.9
To Reproduce
Steps to reproduce the behavior:
Create mysql cluster with setting topology=orc/orc-proxysql yamls below
orc.yaml.txt
mysqlorc.yaml.txt
check cluster status
report-cluster-orcproxy02-2025-01-17-18-36-23.zip
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: