[BUG]Failed to scale-in of asmysql-orc cluster

[tianyue86]

Describe the bug

Kubernetes: v1.31.1-aliyun.1
KubeBlocks: 1.0.0-beta.33
kbcli: 1.0.0-beta.15

To Reproduce
Steps to reproduce the behavior:

1. Create asmysql-orc cluster with yaml below

apiVersion: apps.kubeblocks.io/v1
kind: Cluster
metadata:
  name: orcm-hcagop
  namespace: default
spec:
  clusterDef: orchestrator
  topology: raft
  terminationPolicy: WipeOut
  services:
    - name: orchestrator
      componentSelector: orchestrator
      spec:
        ports:
          - name: orc-http
            port: 80
  componentSpecs:
    - name: orchestrator
      serviceVersion: 3.2.6
      replicas: 3
      resources:
        requests:
          cpu: 500m
          memory: 0.5Gi
        limits:
          cpu: 500m
          memory: 0.5Gi
      volumeClaimTemplates:
        - name: data
          spec:
            accessModes:
              - ReadWriteOnce
            resources:
              requests:
                storage: 20Gi
-------------------------------------
apiVersion: apps.kubeblocks.io/v1
kind: Cluster
metadata:
  name: asmysql-hcagop
  namespace: default
spec:
  clusterDef: mysql
  topology: orc
  terminationPolicy: WipeOut
  componentSpecs:
    - name: mysql
      serviceVersion: 8.0.30
      
      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-hcagop
          service:
            component: orchestrator
            service: orchestrator
            port: orc-http
          credential:
            component: orchestrator
            name: orchestrator

2.scale-out and scale-in

kbcli cluster scale-out asmysql-hcagop --auto-approve --force=true --components mysql --replicas 1  --namespace default
OpsRequest asmysql-hcagop-horizontalscaling-vw7pn created successfully, you can view the progress:
	kbcli cluster describe-ops asmysql-hcagop-horizontalscaling-vw7pn -n default

kbcli cluster list-instances asmysql-hcagop --namespace default        
NAME                     NAMESPACE   CLUSTER          COMPONENT   STATUS    ROLE        ACCESSMODE   AZ                 CPU(REQUEST/LIMIT)   MEMORY(REQUEST/LIMIT)   STORAGE     NODE                                   CREATED-TIME                 
asmysql-hcagop-mysql-0   default     asmysql-hcagop   mysql       Running   primary                  cn-zhangjiakou-c   500m / 500m          512Mi / 512Mi           data:20Gi   cn-zhangjiakou.10.0.0.128/10.0.0.128   Mar 13,2025 17:06 UTC+0800   
asmysql-hcagop-mysql-1   default     asmysql-hcagop   mysql       Running   secondary                cn-zhangjiakou-c   500m / 500m          512Mi / 512Mi           data:20Gi   cn-zhangjiakou.10.0.0.128/10.0.0.128   Mar 13,2025 17:06 UTC+0800   
asmysql-hcagop-mysql-2   default     asmysql-hcagop   mysql       Running   secondary                cn-zhangjiakou-c   500m / 500m          512Mi / 512Mi           data:20Gi   cn-zhangjiakou.10.0.0.128/10.0.0.128   Mar 13,2025 17:10 UTC+0800   

kbcli cluster scale-in asmysql-hcagop --auto-approve --force=true --components mysql --replicas 1  --namespace default 
OpsRequest asmysql-hcagop-horizontalscaling-7txhb created successfully, you can view the progress:
	kbcli cluster describe-ops asmysql-hcagop-horizontalscaling-7txhb -n default

3. Check ops status ===> scale-in is always in running state

kbcli cluster list-ops asmysql-hcagop --status all  --namespace default
NAME                                     NAMESPACE   TYPE                CLUSTER          COMPONENT   STATUS    PROGRESS   CREATED-TIME                 
asmysql-hcagop-horizontalscaling-vw7pn   default     HorizontalScaling   asmysql-hcagop   mysql       Succeed   1/1        Mar 13,2025 17:10 UTC+0800   
asmysql-hcagop-horizontalscaling-7txhb   default     HorizontalScaling   asmysql-hcagop   mysql       Running   0/1        Mar 13,2025 17:13 UTC+0800

4. See error
   2025-03-13T09:21:05.111Z INFO build error: requeue after: 1s as: [http error occurred when executing action memberLeave at pod asmysql-hcagop-mysql-2: unexpected http status code: 503 Service Unavailable] {"controller": "component", "controllerGroup": "apps.kubeblocks.io", "controllerKind": "Component", "Component": {"name":"asmysql-hcagop-mysql","namespace":"default"}, "namespace": "default", "name": "asmysql-hcagop-mysql", "reconcileID": "0fe55c21-431a-4b75-bd2a-ca3cf0b0ab5b", "component": {"name":"asmysql-hcagop-mysql","namespace":"default"}}
   2025-03-13T09:21:05.118Z INFO reconcile object *v1.Component with action STATUS OK {"controller": "component", "controllerGroup": "apps.kubeblocks.io", "controllerKind": "Component", "Component": {"name":"asmysql-hcagop-mysql","namespace":"default"}, "namespace": "default", "name": "asmysql-hcagop-mysql", "reconcileID": "0fe55c21-431a-4b75-bd2a-ca3cf0b0ab5b", "component": {"name":"asmysql-hcagop-mysql","namespace":"default"}}
   2025-03-13T09:21:05.450Z INFO expected cm object[default/sidecar-mysql8.0-reload-script-asmysql-vknysl] has been unchanged

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.