IoTEdge deployment reporting success query not always resulting 200

In certain scenarios (like you remove a latest deployment from edge deployments), as documented system takes on the next available highest priority deployment and applies it; but it does not update the reporting success value.

Query

select deviceId from devices.modules where moduleId = '$edgeAgent' and configurations.[[iotdeploymentid123]].status = 'Applied' and properties.desired.$version = properties.reported.lastDesiredVersion and properties.reported.lastDesiredStatus.code = 200

It seems, system is not updating "properties.reported.lastDesiredStatus.code" value to 200.
If I do an edgeAgent restart from edge, properties.reported.lastDesiredStatus.code gets applied to 200

António Sérgio Azevedo 7,666 Reputation points Microsoft Employee

2020-12-21T12:02:05.337+00:00

@GopikrishnanBahuleyan-2250 thank you for reporting this.

We are looking into this behavior. Can you confirm that you can reproduce this consistently?

1 - For this deployment [iotdeploymentid123] , if you apply it with the highest priority (without being applied when another higher priority deployment is deleted), then properties.reported.lastDesiredStatus.code = 200 without you needing to restart edgeAgent ?
Gopikrishnan Bahuleyan Pillai 31 Reputation points

2020-12-22T13:50:06.327+00:00
Hi @António Sérgio Azevedo

Even If I apply it with a higher priority , statuscode does not not get updated to 200.

As example, current priority is 1 and properties.reported.lastDesiredStatus.code is not yet available. Nothing happens if I

Change the priority of iotdeploymentid123 to 2

Clone the deployment iotdeploymentid123 and make iotdeploymentid123-2 and make the cloned ones priority to a higher one.

But, if the clone or a create new deployment has some considerable changes(like module version update), it always works as expected and reports 200.
António Sérgio Azevedo 7,666 Reputation points Microsoft Employee

2020-12-29T00:01:44.7+00:00

@GopikrishnanBahuleyan-2250 ,
Just want to double check that you tried changing priority to 0 instead of 2? "Priority is determined by setting a number 0-9, where 0 is top priority."

Thanks
Gopikrishnan Bahuleyan Pillai 31 Reputation points

2021-01-04T15:26:01.14+00:00

Hi
Documentation says "A priority defines whether a deployment should be applied to a targeted device relative to other deployments. A deployment priority is a positive integer, with larger numbers denoting higher priority"

module-deployment-monitoring
António Sérgio Azevedo 7,666 Reputation points Microsoft Employee

2021-01-04T17:11:49.83+00:00

**Comment 1/2

@GopikrishnanBahuleyan-2250 ,

Because the deployment manifest describes the modules to be configured on the targeted IoT Edge devices and checks for the configuration metadata: Version; Type; Status (for example, running or stopped); Restart policy; Image and container registry; Routes for data input and output.

I wouldn't expect that [EdgeHub reported properties lastDesiredStatus.code "is triggered" when only the deployment priority is changed.
António Sérgio Azevedo 7,666 Reputation points Microsoft Employee

2021-01-04T17:15:17.937+00:00

**Comment 2/2

To validate if this is by-design we will need to have access to your deployment manifest and check internally if there are any service-side issues with your IoTHub.

If you have a support plan you may Create an Azure support request, else could you please send an email to azcommunity@microsoft.com with the below details, so that we can create a one-time-free support request for you to work closely on this matter?

Thread URL: Link to this thread.
Your Azure Subscription ID:
Email Subject : Attn asergaz

Please let me know the support request number or when the email is sent.

Thank you so much!
Gopikrishnan Bahuleyan Pillai 31 Reputation points

2021-01-05T12:22:32.433+00:00

Hi @António Sérgio Azevedo

Support request created. Case 121010526001783
António Sérgio Azevedo 7,666 Reputation points Microsoft Employee

2021-01-06T11:49:26.627+00:00

Thank you so much.
Once the case is resolved we will post here the answer for benefit of the entire community.

1 answer

António Sérgio Azevedo 7,666 Reputation points Microsoft Employee

2021-03-11T01:05:06.07+00:00
Hello @Gopikrishnan Bahuleyan Pillai ,
As per discussion in the Azure Support Ticket we are now posting the answer publicly. Please mark it as answer.

"
Reported Success will only happen if the Edge Device is notified of a change. Edge is only notified of a change if there is a version change on the twin. IoTHub is smart enough to not change the twin version if there are no changes made to the modules, so this behavior is intended.

Reported Success is the correct metric to use, it may take a few minutes to update, but if there is a twin version change the metric will update.

So basically, there is no such thing as an update that doesn't contain any changes. If an identical deployment is pushed to IoTHub, no version change will happen and any edge devices won't be notified. If there is a version change, Reported Success will update
"

Thank you so much for all your feedback!

Remember:

Please accept an answer if correct. Original posters help the community find answers faster by identifying the correct answer. Here is how.

Want a reminder to come back and check responses? Here is how to subscribe to a notification.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Share via

IoTEdge deployment reporting success query not always resulting 200

1 answer