[Bug]: indexnode panic when upgrade from 2.2.3 to 2.2.8

[bingbb47]

Is there an existing issue for this?

• [X] I have searched the existing issues

Environment

- Milvus version:2.2.8
- Deployment mode(standalone or 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

look likes something wrong about aws s3 but upgrade without s3 config change, and the panic only occured on indexnode

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

indexnode.log

Anything else?

No response

[yanliang567]

/assign @longjiquan /unassign

[yanliang567]

but reproduced in house without aws s3

[xiaocai2333]

but reproduced in house without aws s3

@bingbb47 indexnode is stateless, please check your own environment configuration.

@yanliang567 if you reproduced it, please upload the log.

[xiaocai2333]

Guess the cause of the panic is the same as #25129 , the wrong use of the noexcept keyword.

[xiaocai2333]

has been fixed. /unassign /assign @yanliang567

[yanliang567]

@bingbb47 could you please retry on milvus v.2.2.12? /assign @bingbb47 /unassign

[bingbb47]

@bingbb47 could you please retry on milvus v.2.2.12? /assign @bingbb47 /unassign

This problem seems to have some random factors, and has not been discovered since v2.2.8 version

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. Rotten issues close after 30d of inactivity. Reopen the issue with /reopen.