[Bug]: After upgrading image from master to master, the streamingNode keeps panic: vchannel xx has no schemas in recovery info

[ThreadDao]

Is there an existing issue for this?

• I have searched the existing issues

Environment

- Milvus version: master-20250722-5a109230-amd64 -> master-20250723-1cf8ed50-amd64
- Deployment mode(standalone or cluster): cluster
- MQ type(rocksmq, pulsar or kafka):    
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS): 
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior

upgrading image from master-20250722-5a109230-amd64 -> master-20250723-1cf8ed50-amd64, streamingNode panic

sn_n7pq4.log

Expected Behavior

No response

Steps To Reproduce

Milvus Log

pods:

zong-import-op-49-8717-milvus-datanode-54b7bd5d4b-h9g4b           1/1     Running            0                 4m36s   10.104.23.72    4am-node27   <none>           <none>
zong-import-op-49-8717-milvus-datanode-54b7bd5d4b-kkrx7           1/1     Running            0                 5m16s   10.104.32.70    4am-node39   <none>           <none>
zong-import-op-49-8717-milvus-mixcoord-96857699-6mv8b             1/1     Running            0                 5m44s   10.104.14.92    4am-node18   <none>           <none>
zong-import-op-49-8717-milvus-proxy-674596748c-jcf5r              1/1     Running            0                 45h     10.104.23.151   4am-node27   <none>           <none>
zong-import-op-49-8717-milvus-querynode-0-68b7ffcd4d-4qfp6        1/1     Running            0                 44h     10.104.24.149   4am-node29   <none>           <none>
zong-import-op-49-8717-milvus-querynode-0-68b7ffcd4d-b6r65        1/1     Running            0                 44h     10.104.32.66    4am-node39   <none>           <none>
zong-import-op-49-8717-milvus-querynode-0-68b7ffcd4d-vlbmp        1/1     Running            0                 45h     10.104.21.156   4am-node24   <none>           <none>
zong-import-op-49-8717-milvus-streamingnode-6c67b5d5bc-n7pq4      0/1     CrashLoopBackOff   5 (73s ago)       4m41s   10.104.14.93    4am-node18   <none>           <none>
zong-import-op-49-8717-milvus-streamingnode-8494fdfd6c-wpql5      1/1     Running            0                 45h     10.104.32.63    4am-node39   <none>           <none>

Anything else?

No response

[chyezh]

We don't promise the safe upgrading from 2.6.0-rc.1 to 2.6.0.
A birdwatcher tool is provided to fix the problem before upgrading from 2.6.0-rc.1 to 2.6.0.
milvus-io/birdwatcher#409

/assign @ThreadDao
/unassign

[yanliang567]

@chyezh but the source image here is master-20250722-5a109230-amd64, only two days before the target. This is valid if we need to support v2.6.0 to v2.6.1.

/assign @chyezh
/unassign @ThreadDao

[chyezh]

@yanliang567 The PR that cause the upgrading break is #43500
The Commit history is 2.6.0-rc.1 -> 5a109230 -> (e9ab73e #43500) -> 1cf8ed50 -> 2.6.0 -> 2.6.1.
So the breaking only happens when 2.6.0-rc.1 to 2.6.0, but not 2.6.0 -> 2.6.1.

/assign @ThreadDao
/unassign