downloader improvements during outages#2033
Conversation
Signed-off-by: eriknordmark <erik@zededa.com>
Signed-off-by: eriknordmark <erik@zededa.com>
Signed-off-by: eriknordmark <erik@zededa.com>
Signed-off-by: eriknordmark <erik@zededa.com>
Signed-off-by: eriknordmark <erik@zededa.com>
rvs
left a comment
There was a problem hiding this comment.
Oooph -- this is a bit complex -- need more time to properly review this.
In the meantime -- let it test!
|
Interfaces don't seem to return from an error state during verify. I add modifications for adam: lf-edge/adam#88 and apply diff to your PR and it works fine: |
Signed-off-by: eriknordmark <erik@zededa.com>
Thanks for explaining this. |
|
@rvs do you still need more time to review? |
|
LGTM! Thanks for being patient @eriknordmark ! Lets merge this |
If we have 100% packet loss on one interface, then we still try to use it for every POST to zedcloud. Since we are sending info messages for the device, apps, volumes, content-trees, and blobs, it means that EVE can be far behind in terms of reporting things to zedcloud. The first commit addresses that by using the test status from nim.
As we retry the state transitions seen by the controller are confusing, since the error is cleared when a retry starts. With these changes we don't clear it until the retry has succedded. Also, the log messages include that 1) the operation will be retried in N seconds, and 2) "retry N" has started
Each commit can be reviewed separately.