varunpuranik
commented
6 years ago Module identity life cycle is managed by the Edge runtime (specifically the EdgeAgent) when it is deployed on the device. When you remove/add modules in the portal (during the SetModules operation), it simply changes the edgeAgent twin (which contains the deployment), it doesn't actually delete the identities of the modules. Furthermore, if the module was not created by the EdgeAgent (but was created by the user), then it doesn't delete its identity. It is up to the the user to delete its identity.
Did you create the identities of these modules? If not, was EdgeAgent running for this device? And if you did not create the identities of these modules and EdgeAgent was running on the device, can you send us the EdgeAgent logs... that might tell us why it didn't delete the identities of the modules.
jason-e-gross
OS version and architecture used: ALL
Version used: Latest (1.16.x-preview-004)
Description of the issue:
When Using
registryManager.GetModulesOnDeviceAsyncor.CreateQuery("("SELECT * FROM devices.modules WHERE deviceId='XXXX'");They return modules that are no longer on the device. If we add a module, use it for a bit, then remove it (through the Azure Portal) -- the module twin that was removed is still returned with this - even weeks and months later.
The module isn't listed in the $edgeAgent's modules section of reported/desired properties. The module isn't listed in the IOT Edge section for the device in Azure Portal. The module isn't physically on the device's docker container or images - but yet these commands bring its module twin back in the query. For all intents and purposes - this module is no longer part of our system or function - but still comes back in this query, making the queries useless to us -- we can't programmatically iterate through modules on a device and depend on this information.
Imagine deleting a row in a database table, but always getting that row back every time we query the table. That's what this is.
Why would I want to see a module that I added two months ago, removed 1.5 months ago - show up in a query to get me the modules for a device? Of what use is this?
Imagine deleting a row in a database table, but always getting that row back every time we query the table. That's what this is. Why would Microsoft be hanging on and reporting this information, when it's of no use to us.