[BUG] apecloud-mysql scale-out failed, ITS replicas does not update.

[shanshanying]

KubeBlocks: 1.0.0-beta.2

1. install apecloud-mysql from KB-adodn main branch
2. create a cluster

apiVersion: apps.kubeblocks.io/v1
kind: Cluster
metadata:
  creationTimestamp: "2024-11-15T09:31:35Z"
  finalizers:
  - cluster.kubeblocks.io/finalizer
  generation: 3
  labels:
    auditLogEnabled: "false"
    clusterdefinition.kubeblocks.io/name: apecloud-mysql
  name: acmysql-cluster
  namespace: default
  resourceVersion: "1229118"
  uid: 7792ae81-82db-4bdc-a4fc-516f22b10266
spec:
  clusterDef: apecloud-mysql
  componentSpecs:
  - componentDef: apecloud-mysql-1.0.0-alpha.0
    disableExporter: true
    name: mysql
    replicas: 1
    resources:
      limits:
        cpu: 500m
        memory: 512Mi
      requests:
        cpu: 500m
        memory: 512Mi
    serviceVersion: 8.0.30
    volumeClaimTemplates:
    - name: data
      spec:
        accessModes:
        - ReadWriteOnce
        resources:
          requests:
            storage: 20Gi
        storageClassName: ""
  terminationPolicy: Delete
  topology: apecloud-mysql

4. wait till it is running
5. hscal, update replcias from 1 to 2
6. cluster goes updaging, cmp goes updating, but its replicas is still 1

NAME                                         CLUSTER-DEFINITION   TERMINATION-POLICY   STATUS     AGE
cluster.apps.kubeblocks.io/acmysql-cluster   apecloud-mysql       Delete               Updating   17m

NAME                                                 DEFINITION                     SERVICE-VERSION   STATUS     AGE
component.apps.kubeblocks.io/acmysql-cluster-mysql   apecloud-mysql-1.0.0-alpha.0   8.0.30            Updating   17m

NAME                                                        LEADER                    READY   REPLICAS   AGE
instanceset.workloads.kubeblocks.io/acmysql-cluster-mysql   acmysql-cluster-mysql-0   1       1          17m

NAME                          READY   STATUS    RESTARTS   AGE
pod/acmysql-cluster-mysql-0   4/4     Running   0          17m

8. a new POD is created doing backup
9. backup complted

[shanshanying]

Backup for H-Scale missing ownerreference.
check the bakcup yaml attached.
backup.txt