Failed to trigger some device service autoevent resources during target reboot

[TuhinDasgupta-eaton]

@iain-anderson We are facing a flaky EdgeX service issue where some of the device autoevents doesn't get triggered when we reboot the target. It has been found that whenever our sdk tries to add device to metadata through edgex_add_device API, there is a device existing check inside that and if the device exists already, then an API edgex_device_release gets called which further calls edgex_device_autoevent_stop. If suppose the respective device autoevents are already invoked and running, it stops all autoevents and further no autoevent gets called ever. Due to this we are getting 502 error while trying to acquire untriggered autoevent resources value from edgex developer's UI. Kindly share your thoughts on this issue...

[TuhinDasgupta-eaton]

@iain-anderson We are facing a flaky EdgeX service issue where some of the device autoevents doesn't get triggered when we reboot the target. It has been found that whenever our sdk tries to add device to metadata through edgex_add_device API, there is a device existing check inside that and if the device exists already, then an API edgex_device_release gets called which further calls edgex_device_autoevent_stop. If suppose the respective device autoevents are already invoked and running, it stops all autoevents and further no autoevent gets called ever. Due to this we are getting 502 error while trying to acquire untriggered autoevent resources value from edgex developer's UI. Kindly share your thoughts on this issue...

I have also raised a pull request: edgexfoundry/device-sdk-c#445 to address this. I checked this locally at my end by flashing into the target machine. This currently resolves the issue at my end which I was facing.