Browse Source
Prevent unresolved update status on a failed OTA update (#263)
dashboard-v0.3.11
Mayank Chhabra
4 years ago
committed by
GitHub
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with
13 additions and
0 deletions
-
scripts/update/update
|
|
@ -125,4 +125,17 @@ echo "Deleting cloned repository" |
|
|
echo "Removing lock" |
|
|
echo "Removing lock" |
|
|
rm -f "$UMBREL_ROOT"/statuses/update-in-progress |
|
|
rm -f "$UMBREL_ROOT"/statuses/update-in-progress |
|
|
|
|
|
|
|
|
|
|
|
# Make sure the update-status file isn't stuck in an |
|
|
|
|
|
# unresolved state (i.e anything except "success" or "failed") |
|
|
|
|
|
|
|
|
|
|
|
update_state=$(cat "${UMBREL_ROOT}/statuses/update-status.json" | jq .state -r) |
|
|
|
|
|
|
|
|
|
|
|
if [[ "${update_state}" != "success" ]] && [[ "${update_state}" != "failed" ]]; then |
|
|
|
|
|
# Sleep for a few seconds to make sure the user is on the update view |
|
|
|
|
|
sleep 8 |
|
|
|
|
|
cat <<EOF > "${UMBREL_ROOT}/statuses/update-status.json" |
|
|
|
|
|
{"state": "failed", "progress": 100, "description": "An unexpected error occured", "updateTo": ""} |
|
|
|
|
|
EOF |
|
|
|
|
|
fi |
|
|
|
|
|
|
|
|
exit 0 |
|
|
exit 0 |
|
|
|
