[BUG] mongodb-sharding cluster stop -> start mongos crash

[JashBook]

Describe the bug
A clear and concise description of what the bug is.

 helm get notes -n kb-system kb-addon-mongodb 
NOTES:
Release Information:
  Commit ID: "a6b80f26fc9bf78796e837a6d60b50993dac3d15"
  Commit Time: "2025-12-02 17:26:34 +0800"
  Release Branch: "v1.1.0-alpha.5"
  Release Time:  "2025-12-15 09:39:54 +0800"
  Enterprise: "false"

➜  ~ kbcli version
Kubernetes: v1.30.4-vke.10
KubeBlocks: 1.1.0-alpha.5
kbcli: 1.0.2-beta.0

To Reproduce
Steps to reproduce the behavior:

1. create cluster

apiVersion: apps.kubeblocks.io/v1
kind: Cluster
metadata:
  name: mongodbs-ossqmq
  namespace: default
spec:
  clusterDef: mongodb
  topology: sharding
  terminationPolicy: DoNotTerminate
  shardings:
    - name: shard
      shards: 3
      template:
        name: mongodb
        serviceVersion: 5.0.29
        replicas: 3
        disableExporter: false
        env:
          - name: SHARDING_NAME
            value: shard
        resources:
          requests:
            cpu: 100m
            memory: 0.5Gi
          limits:
            cpu: 100m
            memory: 0.5Gi
        volumeClaimTemplates:
          - name: data
            spec:
              storageClassName: 
              accessModes:
                - ReadWriteOnce
              resources:
                requests:
                  storage: 20Gi
  componentSpecs:
    - name: config-server
      serviceVersion: 5.0.29
      replicas: 3
      disableExporter: false
      systemAccounts:
      - name: root
        passwordConfig:
          length: 16
          numDigits: 8
          numSymbols: 0
          letterCase: MixedCases
          seed: mongodbs-ossqmq
      env:
        - name: MONGODB_BALANCER_ENABLED
          value: "false"
      resources:
        limits:
          cpu: 100m
          memory: 0.5Gi
        requests:
          cpu: 100m
          memory: 0.5Gi
      volumeClaimTemplates:
        - name: data
          spec:
            storageClassName: 
            accessModes:
              - ReadWriteOnce
            resources:
              requests:
                storage: 20Gi
    - name: mongos
      serviceVersion: 5.0.29
      replicas: 3
      disableExporter: false
      env:
        - name: MONGODB_BALANCER_ENABLED
          value: "false"
      resources:
        limits:
          cpu: 100m
          memory: 0.5Gi
        requests:
          cpu: 100m
          memory: 0.5Gi

2. stop

kbcli cluster stop mongodbs-ossqmq --auto-approve --force=true

3. start

kbcli cluster start mongodbs-ossqmq --force=true

4. See error

kubectl get cluster mongodbs-ossqmq 
NAME              CLUSTER-DEFINITION   TERMINATION-POLICY   STATUS     AGE
mongodbs-ossqmq   mongodb              DoNotTerminate       Abnormal   17m
➜  ~ 
➜  ~ kubectl get ops -l app.kubernetes.io/instance=mongodbs-ossqmq
NAME                          TYPE    CLUSTER           STATUS    PROGRESS   AGE
mongodbs-ossqmq-start-r6pd8   Start   mongodbs-ossqmq   Running   0/15       4m45s
➜  ~ 
➜  ~ kubectl get pod -l app.kubernetes.io/instance=mongodbs-ossqmq
NAME                       READY   STATUS             RESTARTS       AGE
mongodbs-ossqmq-mongos-0   1/2     CrashLoopBackOff   5 (96s ago)    4m51s
mongodbs-ossqmq-mongos-1   1/2     CrashLoopBackOff   5 (106s ago)   4m48s
mongodbs-ossqmq-mongos-2   1/2     CrashLoopBackOff   5 (97s ago)    4m45s

logs error pod

kubectl logs mongodbs-ossqmq-mongos-0 --previous 
Defaulted container "mongos" out of: mongos, exporter, init-kubectl (init)
ERROR: No FQDNs provided.
{"t":{"$date":"2025-12-16T09:44:07.663Z"},"s":"F",  "c":"-",        "id":22865,   "ctx":"-","msg":"Error during global initialization","attr":{"error":{"code":9,"codeName":"FailedToParse","errmsg":"Empty host component parsing HostAndPort from \"\""}}}
{"t":{"$date":"2025-12-16T09:44:07.663Z"},"s":"I",  "c":"CONTROL",  "id":23138,   "ctx":"-","msg":"Shutting down","attr":{"exitCode":14}}

kubectl logs mongodbs-ossqmq-mongos-1           
Defaulted container "mongos" out of: mongos, exporter, init-kubectl (init)
ERROR: No FQDNs provided.
{"t":{"$date":"2025-12-16T09:43:57.568Z"},"s":"F",  "c":"-",        "id":22865,   "ctx":"-","msg":"Error during global initialization","attr":{"error":{"code":9,"codeName":"FailedToParse","errmsg":"Empty host component parsing HostAndPort from \"\""}}}
{"t":{"$date":"2025-12-16T09:43:57.568Z"},"s":"I",  "c":"CONTROL",  "id":23138,   "ctx":"-","msg":"Shutting down","attr":{"exitCode":14}}

➜  ~ kubectl logs mongodbs-ossqmq-mongos-2
Defaulted container "mongos" out of: mongos, exporter, init-kubectl (init)
ERROR: No FQDNs provided.
{"t":{"$date":"2025-12-16T09:44:06.475Z"},"s":"F",  "c":"-",        "id":22865,   "ctx":"-","msg":"Error during global initialization","attr":{"error":{"code":9,"codeName":"FailedToParse","errmsg":"Empty host component parsing HostAndPort from \"\""}}}
{"t":{"$date":"2025-12-16T09:44:06.475Z"},"s":"I",  "c":"CONTROL",  "id":23138,   "ctx":"-","msg":"Shutting down","attr":{"exitCode":14}}

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.

[github-actions]

This issue has been marked as stale because it has been open for 30 days with no activity