About dubbo-admin Test provider :No provider available for the service
- Dominant language
- Go
- Stars
- 4.1k
- Forks
- 2.2k
- Avg merge
- 10d 12h
- Merged PRs (30d)
- 4
Description
- [ ] I have searched the [issues](https://github.com/apache/dubbo-admin/issues) of this repository and believe that this is not a duplicate.
- [ ] I have checked the [REAMDE](https://github.com/apache/dubbo-admin/blob/develop/README.md) of this repository and believe that this is not a duplicate.
### Environment
* Dubbo Admin version: 2.7
* Registry center detail (type and version): Zookeeper :laster
* Operating System version: xxx
* Java version: 11.0.16
### Steps to reproduce this issue
1. build run provider
2. dubbo-admin test provider
### Error Message
System Error, please try again later! Message:Failed to check the status of the service xxx.xxx.xxxService. No provider available for the service xxx.xxx.xxxService from the url zookeeper://xxx.xxx.xxx.xxx:xxxx/org.apache.dubbo.registry.RegistryService?anyhost=true&application=dubbo-admin&check=false&deprecated=false&dubbo=2.0.2&dynamic=true&generic=true&interface=xxx.xxx.xxxService&lazy=false&metadata-type=remote&methods=getAllRoles&pid=1®ister.ip=172.17.0.3&release=2.7.2&remote.application=mp-system&side=consumer&sticky=false×tamp=1673918744676 to the consumer 172.17.0.3 use dubbo version 2.7.2
Pls. provide [GitHub address] to reproduce this issue.
### Expected Result
What do you expected from the above steps?
### Actual Result
What actually happens?
If there is an exception, please attach the exception trace:
```
Just put your stack trace here!
```
Contributor guide
Research direction
The report names no files, tests, or entry points. Start by reproducing the listed provider build/run and Dubbo Admin test-provider steps with Java 11 and the stated registry setup; the issue needs a concrete expected result, actual result, and reproducible environment before a change can be scoped.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100