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]asmysql-orc cluster failed when setting serviceVersion: 5.7.44 #8938

Closed
tianyue86 opened this issue Feb 17, 2025 · 1 comment · Fixed by apecloud/kubeblocks-addons#1475
Assignees
Labels
kind/bug Something isn't working
Milestone

Comments

@tianyue86
Copy link

Describe the bug
Kubernetes: v1.31.1-aliyun.1
KubeBlocks: 1.0.0-beta.28
kbcli: 1.0.0-beta.13

To Reproduce
Steps to reproduce the behavior:

  1. Create orc cluster in running status
k get cluster -A
NAMESPACE   NAME                         CLUSTER-DEFINITION   TERMINATION-POLICY   STATUS     AGE
default     orcm-evhxjd                  orchestrator         WipeOut              Running    29m
  1. Create mysql-orc cluster with yaml below: set serviceVersion: 5.7.44
apiVersion: apps.kubeblocks.io/v1
kind: Cluster
metadata:
  name: asmysql-evhxjd
  namespace: default
spec:
  clusterDef: mysql
  topology: orc
  terminationPolicy: Delete
  componentSpecs:
    - name: mysql
      serviceVersion: 5.7.44

      disableExporter: true
      replicas: 2
      resources:
        limits:
          cpu: 500m
          memory: 0.5Gi
        requests:
          cpu: 500m
          memory: 0.5Gi
      volumeClaimTemplates:
        - name: data
          spec:
            accessModes:
              - ReadWriteOnce
            resources:
              requests:
                storage: 20Gi
      serviceRefs:
      - name: orchestrator
        namespace: default
        clusterServiceSelector:
          cluster: orcm-evhxjd
          service:
            component: orchestrator
            service: orchestrator
            port: orc-http
          credential:
            component: orchestrator
            name: orchestrator
  1. Create mysql-orc cluster with yaml below: set serviceVersion: 8.0.33
apiVersion: apps.kubeblocks.io/v1
kind: Cluster
metadata:
  name: asmysql-evhxjd2
  namespace: default
spec:
  clusterDef: mysql
  topology: orc
  terminationPolicy: Delete
  componentSpecs:
    - name: mysql
      serviceVersion: 8.0.33

      disableExporter: true
      replicas: 2
      resources:
        limits:
          cpu: 500m
          memory: 0.5Gi
        requests:
          cpu: 500m
          memory: 0.5Gi
      volumeClaimTemplates:
        - name: data
          spec:
            accessModes:
              - ReadWriteOnce
            resources:
              requests:
                storage: 20Gi
      serviceRefs:
      - name: orchestrator
        namespace: default
        clusterServiceSelector:
          cluster: orcm-evhxjd
          service:
            component: orchestrator
            service: orchestrator
            port: orc-http
          credential:
            component: orchestrator
            name: orchestrator
  1. check cluster status
===>asmysql cluster failed when setting serviceVersion: 5.7.44
k get cluster -A
NAMESPACE   NAME                         CLUSTER-DEFINITION   TERMINATION-POLICY   STATUS     AGE
default     asmysql-evhxjd               mysql                Delete               Failed     16m
default     asmysql-evhxjd2              mysql                Delete               Running    5m15s

k get cmpd
mysql-orc-5.7-1.0.0-alpha.0               mysql              5.7.44            Available   6d2h
mysql-orc-8.0-1.0.0-alpha.0               mysql              8.0.33            Available   6d2h
  1. describe cmp
k describe cmp asmysql-evhxjd-mysql
Status:
  Conditions:
    Last Transition Time:  2025-02-17T06:58:26Z
    Message:               The operator has started the provisioning of Cluster: asmysql-evhxjd-mysql
    Observed Generation:   1
    Reason:                PreCheckSucceed
    Status:                True
    Type:                  ProvisioningStarted
    Last Transition Time:  2025-02-17T06:59:51Z
    Message:               the component phase is Failed
    Observed Generation:   1
    Reason:                Unavailable
    Status:                False
    Type:                  Available
  Message:
    InstanceSet/asmysql-evhxjd-mysql:  Role probe timeout, check whether the application is available
  Observed Generation:                 1
  Phase:                               Failed
Events:
  Type     Reason                    Age                 From                  Message
  ----     ------                    ----                ----                  -------
  Warning  Warning                   20m (x14 over 21m)  component-controller  precondition check error, runtime is not ready
  Warning  Requeue                   20m                 component-controller  requeue to waiting for post-provision annotation to be set
  Normal   ComponentPhaseTransition  20m                 component-controller  component is Creating
  Normal   Unavailable               20m                 component-controller  the component phase is Creating
  Normal   ComponentPhaseTransition  17m                 component-controller  component is Failed
  Normal   Unavailable               17m                 component-controller  the component phase is Failed

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):

  • 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 Feb 17, 2025
@tianyue86 tianyue86 added this to the Release 1.0.0 milestone Feb 17, 2025
@hanguobiao
Copy link

Image
Caused by exceeding the Master_Host length limit in MySQL 5

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

Successfully merging a pull request may close this issue.

3 participants