-
Notifications
You must be signed in to change notification settings - Fork 485
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Command service API is stuck at first run #2399
Comments
This issue currently causes failure in blackbox-testing. |
This might be a regression introduced by #2370 somewhere in the URLClient code. I don't have any insight or theories beyond that. |
This looks to me like a variation of the original issue that led us down the refactoring path. Possibly newly introduced retry is not working as expected? Assigned to @brandonforster for investigation/solution. |
It looks like logging is throwing an error retrieving its configuration from Consul. I'd say there's two issues here:
|
I believe I have identified the issue in contracts. Submitting a PR now, I'll use this issue number to update the core-contracts version. |
Closed by edgexfoundry/go-mod-core-contracts#220 |
Reopening, adding a PR to incorporate those changes into the codebase and fix the BB tests. |
Signed-off-by: Brandon Forster <me@brandonforster.com>
🐞 Bug Report
Affected Services
The issue is located in: core-commandIs this a regression?
yes, only happen in master branchDescription and Minimal Reproduction
When the command service starts, the first time of executing http://localhost:48082/api/v1/device will be stuck.
https://github.com/edgexfoundry/developer-scripts/blob/master/releases/nightly-build/compose-files/docker-compose-nexus-redis-no-secty.yml
docker-compose -f docker-compose-nexus-redis-no-secty.yml up -d
curl http://localhost:48082/api/v1/device
🔥 Exception or Error
There is no error log in edgex-core-command container.
🌍 Your Environment
Deployment Environment:
EdgeX Version:
Master
Anything else relevant?
Cancel the curl request, and send it again, the request works properly.
Also, this issue could be reproduced by simply restarting command service.
docker-compose -f docker-compose-nexus-redis-no-secty.yml restart command
The text was updated successfully, but these errors were encountered: