milvus: [Bug]: failed to get client address

Is there an existing issue for this?

• I have searched the existing issues

Environment

- Milvus version:2.2.2
- Deployment mode(standalone or cluster): standalone
- MQ type(rocksmq, pulsar or kafka):    
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS): Ubuntu
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior

I ran the upgrade script to upgrade from 2.1 to 2.2, but I’m not sure if it worked. I got:

[2023/02/03 04:00:41.306 +00:00] [WARN] [config/file_source.go:85] ["Read config failed"] [error="read /milvus/configs/migration.yaml: is a directory"]
panic: key not found: etcd.endpoints

goroutine 1 [running]:
github.com/milvus-io/milvus/internal/util/paramtable.(*EtcdConfig).initEndpoints(0xc000455380)
	/home/jenkins/agent/workspace/internal/util/paramtable/service_param.go:142 +0x97
github.com/milvus-io/milvus/internal/util/paramtable.(*EtcdConfig).LoadCfgToMemory(0xc000455380)
	/home/jenkins/agent/workspace/internal/util/paramtable/service_param.go:109 +0x4c
github.com/milvus-io/milvus/cmd/tools/migration/configs.(*MilvusConfig).init(0xc00015ed98, 0xc00054eea0)
	/home/jenkins/agent/workspace/cmd/tools/migration/configs/config.go:93 +0x156
github.com/milvus-io/milvus/cmd/tools/migration/configs.newMilvusConfig(...)
	/home/jenkins/agent/workspace/cmd/tools/migration/configs/config.go:73
github.com/milvus-io/milvus/cmd/tools/migration/configs.(*Config).init(0xc00033d230, {0x7ffd15f75f44?, 0x2?})
	/home/jenkins/agent/workspace/cmd/tools/migration/configs/config.go:121 +0xbb
github.com/milvus-io/milvus/cmd/tools/migration/configs.NewConfig(...)
	/home/jenkins/agent/workspace/cmd/tools/migration/configs/config.go:129
github.com/milvus-io/milvus/cmd/tools/migration/command.Execute({0xc00003c040?, 0x2, 0x2})
	/home/jenkins/agent/workspace/cmd/tools/migration/command/main.go:24 +0x192
main.main()
	/home/jenkins/agent/workspace/cmd/tools/migration/main.go:10 +0x2e

After upgrading, it can’t query the data. I look in the log and I see

["failed to get client address"] [error="find no available rootcoord, check rootcoord state"]

Did the upgrade work? Anyone have any ideas? I’m upgrading because our 2.1 in production started stopping randomly about once a day. I don’t know what is going on, so I’m having quite a bit of trouble. Thanks!

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

milvus.log

Anything else?

No response