Skip to:
Some times, the mender client does not respect the expiration time expressed in a given control update map and ends the deployment before it should.
We have seen very rarely in our CI, but there is evidence that it there must be a bug in the client.
An example of a failure can be found here, where the deployment finalized 4 seconds before it should.
See also the description and referenced test fix from https://tracker.mender.io/browse/QA-503
Seems to be a test bug, and the same found in . I vote for rejecting this one.
PR: https://github.com/mendersoftware/meta-mender/pull/1867
We have an strong theory that there is no bug as such, and we are still dealing with a test issue. See comments in - test_update_control has the same problem with the clocks that described there for test_mender_connect_auth_changes.
FYI
Some times, the mender client does not respect the expiration time expressed in a given control update map and ends the deployment before it should.
We have seen very rarely in our CI, but there is evidence that it there must be a bug in the client.
An example of a failure can be found here, where the deployment finalized 4 seconds before it should.
See also the description and referenced test fix from https://tracker.mender.io/browse/QA-503