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
[DataStorage] can not find device in cache #312
Comments
Hi @t25kim, I replicated the bug. This is happening whenever we try to add a new device also. Example :
This device would not be discovered until we build for the second time. I tried this multiple times and this issue seems to be consistent. I am checking if this was a problem with the Hanoi release or if it needs to be done from our side. |
Thanks @sun-sharma. |
This issue is from EdgeX side, Whenevr the service is started the devices already present in metadata are loaded in cache. But the devices which are added are not addded to cache. Hence this doesnot occur after reboot. I have tried with device-rest.go. Observed the same behaviour. Changes are required in device-sdk of edgex foundry. Files i checked (/internal/provision/devices.go) of device sdk if edgexfoundry. This is called at device startup. |
@nitu-s-gupta What about approaching to EdgeX with me and try resolving this issue? 😄 |
Thanks for your effort! edgex-metadata data
CURL Request$ curl -X 'POST' 'http://localhost:49986/api/v1/callback' -H 'accept: /' -H 'Content-Type: application/json' -d '{"type":"DEVICE","id":"774deba4-5469-4c38-8c2a-93a0f3c08252"}' Edge Orchestration Log
I think edgex would be fixed or we can add some workaround code to datastorage. |
@t25kim How about raising an issue in edgex github of device sdk?, so that it can be updated. Workaround can be done like calling the API. But one more thing I noticed is storagedriver we have callbacks, those should be invoked when the device is added. But that too is not invoked, since the work aorund steps would be included there |
@jpwhitemn Hi, we encouter the issue w.r.t. the data storage that has been related to EdgeX Foundry. Could you introduce us the right person from the EdgeX community to discuss and/or to resolve this topic? 😄 |
I agree to share this issue with edgex. However if the patch isn't implemented on edgex before home edge d-release, let's fix it on Edge Orchestration. |
Signed-off-by: Nitu Gupta <nitu.gupta@samsung.com>
.search-word {
BACKGROUND-COLOR: #ffee94
}
P {
FONT-SIZE: 10pt; MARGIN-BOTTOM: 5px; FONT-FAMILY: Arial, arial; MARGIN-TOP: 5px
}
TD {
FONT-SIZE: 10pt; MARGIN-BOTTOM: 5px; FONT-FAMILY: Arial, arial; MARGIN-TOP: 5px
}
LI {
FONT-SIZE: 10pt; MARGIN-BOTTOM: 5px; FONT-FAMILY: Arial, arial; MARGIN-TOP: 5px
}
BODY {
FONT-SIZE: 10pt; FONT-FAMILY: Arial, arial
}
P {
FONT-SIZE: 10pt; MARGIN-BOTTOM: 5px; FONT-FAMILY: Arial, arial; MARGIN-TOP: 5px
}
Hello Peter,
The issue is not from the EdgeX side. After discussing with Cloud Tsai I understood its the usage of wrong IP address because of which the coredata was not able to invoke the callback and hence the cache not update. For local machine, the issue is resolved by using docker0 IP address as I tested it.
But now the issue is the scenario that Taewan has very well mentioned EdgeX running independently on one device and Edge-Orchestration running on another device connected in network. So this has to be tested irrespective of the cache issue. I m trying to do that similar setup. Though I tested the similar scenario with normal pinging docker (alpine) and was able to setup communication using overlay network. Now I need to try out for the edge-orchestration.
Thanks & Regards
Nitu
--------- Original Message ---------
Sender : Peter Moonki ***@***.***>
Date : 2021-09-07 07:46 (GMT+5:30)
Title : Re: [lf-edge/edge-home-orchestration-go] [DataStorage] can not find device in cache (#312)
To : ***@***.***>
CC : Nitu Sajjanlal ***@***.***>, ***@***.***>
@nitu-s-gupta What do you think of resolving this issue from HomeEdge instead of requesting it at EdgeX, since it seems to me that the rationale of our request conflicts to the existing device-sdk-go at EdgeX?
—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android.
|
Thank you for your kind clarification, @nitu-s-gupta 😄 |
Describe the bug
The edge-orchestration can not find the device in the cache if edge-orchestration registers device configuration to edgex for the first time. It works after reboot.
To Reproduce
Log from edge-orchestration
Test environment configuration (please complete the following information):
The text was updated successfully, but these errors were encountered: