Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG]Failed to create mysql cluster when setting topology: semisync-proxysql #8823

Open
tianyue86 opened this issue Jan 17, 2025 · 1 comment
Assignees
Labels
kind/bug Something isn't working

Comments

@tianyue86
Copy link

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:

  1. Create mysql topology: semisync-proxysql cluster with yaml below
apiVersion: apps.kubeblocks.io/v1
kind: Cluster
metadata:
  name: mysqlsp02
  labels:
    helm.sh/chart: mysql-cluster-1.0.0-alpha.0
    app.kubernetes.io/version: "8.0.33"
    app.kubernetes.io/instance: mysqlsp02
  namespace: default
  annotations:
spec:
  terminationPolicy: Delete
  clusterDef: mysql
  topology: semisync-proxysql
  componentSpecs:
    - name: mysql
      serviceVersion: 8.0.39     
      disableExporter: true     
      replicas: 1     
      resources:
        limits:
          cpu: "0.5"
          memory: "0.5Gi"
        requests:
          cpu: "0.5"
          memory: "0.5Gi"     
      volumeClaimTemplates:
        - name: data
          spec:
            accessModes:
              - ReadWriteOnce
            resources:
              requests:
                storage: 20Gi
    - name: proxysql
      replicas: 1
      resources:
        limits:
          cpu: "1"
          memory: "1Gi"
  1. Check cluster
k get cluster -A
NAMESPACE   NAME           CLUSTER-DEFINITION   TERMINATION-POLICY   STATUS     AGE
default     mysqlsp02      mysql                Delete               Creating   21m

k get pod
NAME                          READY   STATUS    RESTARTS   AGE
mysqlsp02-mysql-0             4/4     Running   0          22m

k get cmp
NAME                        DEFINITION                        SERVICE-VERSION   STATUS     AGE
mysqlsp02-mysql             mysql-8.0-1.0.0-alpha.0           8.0.39            Updating   22m
mysqlsp02-proxysql          mysql-proxysql-1.0.0-alpha.0      2.4.4                        22m
  1. Describe cmp
k describe cmp mysqlsp02-proxysql
Events:
  Type     Reason   Age                 From                  Message
  ----     ------   ----                ----                  -------
  Warning  Warning  66s (x18 over 22m)  component-controller  resolving vars from Service object mysql-server error: service mysql-server not defined in the component definition that component mysql used

k describe cmp mysqlsp02-mysql
Events:
  Type    Reason                    Age                  From                  Message
  ----    ------                    ----                 ----                  -------
  Normal  Unknown                   24m                  component-controller  the component phase is unknown
  Normal  ComponentPhaseTransition  24m (x3 over 24m)    component-controller  component is Creating
  Normal  Unavailable               24m (x3 over 24m)    component-controller  the component phase is Creating
  Normal  ComponentPhaseTransition  4m14s (x5 over 23m)  component-controller  component is Running
  Normal  Available                 4m14s (x5 over 23m)  component-controller  the component phase is Running
  Normal  ComponentPhaseTransition  3m58s (x5 over 23m)  component-controller  component is Updating
  Normal  Unavailable               3m58s (x5 over 23m)  component-controller  the component phase is Updating

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: [e.g. iOS]
  • Browser [e.g. chrome, safari]
  • Version [e.g. 22]

Additional context
Add any other context about the problem here.

@tianyue86 tianyue86 added the kind/bug Something isn't working label Jan 17, 2025
@tianyue86
Copy link
Author

@kubeJocker please take a look at this issue, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants