# When deploy MySQL CR, pod mysql-1 CrashLoopBackOff infinitely

**URL:** <https://forums.percona.com/t/when-deploy-mysql-cr-pod-mysql-1-crashloopbackoff-infinitely/38069>\
**Category:** Percona Operator for MySQL\
**Created:** [May 23, 2025, 3:21am UTC](https://forums.percona.com/t/when-deploy-mysql-cr-pod-mysql-1-crashloopbackoff-infinitely/38069 "2025-05-23T03:21:24Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Andy\_Yu](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/andy_yu/32/20039_2.png) [@Andy\_Yu](https://forums.percona.com/u/Andy_Yu)\
**Post date:** [May 23, 2025, 3:21am UTC](https://forums.percona.com/t/when-deploy-mysql-cr-pod-mysql-1-crashloopbackoff-infinitely/38069/1 "2025-05-23T03:21:24Z")

</div>

## Description:

Hi there~

I am new to Percona Server for MySQL. I have deploy Percona Operator for MySQL(V0.8.0) successfully, and then I try to deploy a MySQL CR by helm with override values. When MySQL chart(V0.8.0) release installed (all components are 3 replicas, please see override file for detailed.), mysql-0 startup normaly, and then haproxy-0/1/2 and orc-0/1/2 startup successfully. By the same time, mysql-1 startup failed and restart automatically and restart infinitely. Below is related information, anything I did wrong or missing?

## Steps to Reproduce:

1. deploy Percona Operator for MySQL
2. Create a MySQL CR using ‘helm install’ with override file(see below additional information session) to deploy a async MySQL cluster  
PS: I can deploy a group replication MySQL cluster successfully, but fail with async mode. All setting in override file are same except the clusterType setting.

## Version:

Kubernetes version: Tanzu TKC V1.29.4  
Percona Operator for MySQL version: V0.8.0  
Percona Server for MySQL version: V0.8.0

## Logs:

Please see attachments for each container logs

- mysql-1-mysql-init.log – Init container logs
- mysql-1-pt-heartbeat.log – heartbeat container logs
- mysql-1-mysql.log – mysql container logs

## Expected Result:

Expect that all MySQL cluster node startup normally.

## Actual Result:

First node mysql-0 startup normally, and then node mysql-1 startup failed and restart infinitely

### Pod status:

```auto
NAME READY STATUS RESTARTS AGE
psdb-ps-db-haproxy-0 2/2 Running 0 6d23h
psdb-ps-db-haproxy-1 2/2 Running 0 6d23h
psdb-ps-db-haproxy-2 2/2 Running 0 6d23h
psdb-ps-db-mysql-0 3/3 Running 0 6d23h
psdb-ps-db-mysql-1 1/3 CrashLoopBackOff 5051 (9s ago) 6d23h
psdb-ps-db-orc-0 2/2 Running 0 6d23h
psdb-ps-db-orc-1 2/2 Running 0 6d23h
psdb-ps-db-orc-2 2/2 Running 0 6d23h
pso-ps-operator-78b5644ddd-prpbq 1/1 Running 0 7d23h

```

## Additional Information:

###Override YAML file for helm install command:

```auto
mysql:
  clusterType: async
  autoRecovery: true
  image:
    repository: percona/percona-server
    tag: 8.0.36-28
  imagePullPolicy: IfNotPresent
  size: 3
  resources:
    requests:
      cpu: 200m
      memory: 512Mi
    limits:
      cpu: 2000m
      memory: 4Gi
  expose:
    enabled: true
    type: LoadBalancer
  volumeSpec:
    pvc:
      resources:
        requests:
          storage: 100G
  labels:
    mysql_cluster: tanzu-test

```

[mysql-1-mysql.log](https://forums.percona.com/uploads/short-url/rfimph0rOclIkUw5FBtgnpn9oYk.log) (27.4 KB)  
[mysql-1-mysql-init.log](https://forums.percona.com/uploads/short-url/dl0OYahFe6ysA9qj3RMGYnyeEZB.log) (3.2 KB)  
[mysql-1-pt-heartbeat.log](https://forums.percona.com/uploads/short-url/vWxil07jwj5KFnsRjagBNI6iFSG.log) (1.2 KB)