josephmsft
commented
1 month ago Is this "InProgress" state persisting continuously for the online devices? What is possibly happening is that if the device remains connected for over an hour, the IoT Hub connection can be refreshed and the agent will receive the ADM configuration again and go into the deployment workflow and report InProgress, but once in the workflow it should see it has the update installed already and report Success again. I would not expect it to stay "InProgress" for an extended period of time.
Was the offline agent ever online to receive the deployment? Or has it been offline the entire time?
mahdighorbanpourptw
agreentree-dmc
jw-msft
I have an update script which is a copy of the sample scripts and some changes to adapt it to our needs. The update works perfectly fine. The state changes from not running, in progress, succeeded. Then after a while, it changes back to In Progress. I looked at the update agent logs and there, the condition check works perfectly fine, and the update is not triggered twice! Note that, when I restart the agent, it immediately shows "Succeeded". Then the same issue, after some time, goes back to in progress. having said, the IotHub portal, updates, update-group overview, showing inconsistent data. The first two devices, are already updated successfully, which on the upper side info box, shows correctly. But in the lower side, all of them are shown "In Progress". The third device in the list is even turned off!
You could also see that, in the twin, it says applied.
Expected behavior
The first two devices should keep showing the state "Succeeded". And the last one, should be "Not Running"
Actual behavior
All the devices are shown "In Progress".
Reproduction Steps
Use the example scripts to create an update. Assign it to the devices.
Environment
Ubuntu 22.04 IotEdge 1.4.39 DeviceIpdate-Agent 1.1.0