-
Notifications
You must be signed in to change notification settings - Fork 41
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
Ignore duplicate deployment workflow not working as expected #609
Comments
I found another use case where the deployment status will be switched back to "in Progress".
Imho, the agent should not touch the last state in case he doesn't do anything... -> Ignoring Retry. currentRetryToken '(NULL)', nextRetryToken '(NULL)' |
Any news about that topic in general? Unfortunately, I haven't found a solution by myself for the use case(#609 (comment)) yet and need pls support here.... |
@JoergZeidler Have you heard anything further on this topic or found a work-around? I am experiencing the same issue. |
@agreentree-dmc |
I guess this is the same error as seen in #625 I did some code investigations please see #625 (comment) |
During long-term testing I encountered an issue with the deployment status.
Expected Behavior
Deployment status should not change even after a token expiry refresh.
Current Behavior
Deployment status changed from Successfully back to In Progress.
Steps to Reproduce
3.1. current update state is succeeded
3.2 deployment status is succeeded (module twin: reported property "state": 0)
5.1. deployments status changed to "in progress" (module twin: reported property "state": 6) -> NOK
5.1. current update state still succeeded
Device Information
DU Agent Version 1.1.0
Logs
token expiry connection refresh changed deployment status to "in progress"
log.txt
cutout:
Ignoring duplicate deployment 6409ddb9d8ce39ade510df4a-20242685040, action 3
Additional Information
PR to fix the issue
The text was updated successfully, but these errors were encountered: