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]The mysql-orc cluster created failed, even though the ORC cluster is already in running status #8907

Closed
tianyue86 opened this issue Feb 11, 2025 · 1 comment
Assignees
Labels
kind/bug Something isn't working
Milestone

Comments

@tianyue86
Copy link

Describe the env
Kubernetes: v1.31.1-aliyun.1
KubeBlocks: 1.0.0-beta.28
kbcli: 1.0.0-beta.11

To Reproduce
Steps to reproduce the behavior:

  1. create orchestrator cluster
    default orclu02 orchestrator Delete Running 16m
  2. create mysql-orc cluster
apiVersion: apps.kubeblocks.io/v1
kind: Cluster
metadata:
  name: mysql-cluster
  namespace: default
spec:
  terminationPolicy: Delete
  componentSpecs:
    - name: mysql
      componentDef: mysql-orc-8.0 # use componentDef: mysql-orc-8.0
      disableExporter: true
      serviceVersion: "8.0.35"
      replicas: 2
      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
      serviceRefs:
        - name: orchestrator
          namespace: default # set to your orchestrator cluster namespace
          clusterServiceSelector:
            cluster:  orclu02  # set to your orchestrator cluster name
            service:
              component: orchestrator
              service: orchestrator
              port:  orc-http
            credential:
              component: orchestrator
              name: orchestrator
  1. check cluster status
k get cluster -A
NAMESPACE   NAME                   CLUSTER-DEFINITION   TERMINATION-POLICY   STATUS     AGE
default     mysql-cluster                               Delete                          8m45s
default     orclu02                orchestrator         Delete               Running    21m

k get cmpd|grep mysql
apecloud-mysql-1.0.0-alpha.0        mysql              8.0.30            Available     5h4m
mysql-5.7-1.0.0-alpha.0             mysql              5.7.44            Available     5h4m
mysql-8.0-1.0.0-alpha.0             mysql              8.0.33            Available     5h4m
mysql-8.4-1.0.0-alpha.0             mysql              8.4.2             Available     5h4m
mysql-mgr-8.0-1.0.0-alpha.0         mysql              8.0.33            Available     5h4m
mysql-mgr-8.4-1.0.0-alpha.0         mysql              8.4.2             Available     5h4m
mysql-orc-5.7-1.0.0-alpha.0         mysql              5.7.44            Available     5h4m
mysql-orc-8.0-1.0.0-alpha.0         mysql              8.0.33            Available     5h4m
proxysql-mysql-1.0.0-alpha.0        proxysql           2.4.4             Available     5h4m

  1. See error
    2025-02-11T09:42:01.503Z INFO build error: requeue after: 1s as: build synthesized component failed at pre-terminate transformer: build service references failed: Component.apps.kubeblocks.io "myorc-orchestrator" not found {"controller": "component", "controllerGroup": "apps.kubeblocks.io", "controllerKind": "Component", "Component": {"name":"mysql-cluster-mysql","namespace":"default"}, "namespace": "default", "name": "mysql-cluster-mysql", "reconcileID": "7f6e1498-5e1c-4944-9564-5157f1fae356", "component": {"name":"mysql-cluster-mysql","namespace":"default"}}

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

After cleaning up environment, the cluster works as expected. Thanks @hanguobiao for the investigation.

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