44r0n7/pi-kit
1
0
Fork 0
Code Issues 8 Pull Requests Actions Packages Projects Releases 10 Wiki Activity

Rollback sometimes fails after update #1

New Issue
Closed
opened 2025-12-11 03:55:02 +00:00 by 44r0n7 · 0 comments
44r0n7 commented 2025-12-11 03:55:02 +00:00
Owner
Copy Link

Problem
After updating to 0.1.0-dev1 via the dashboard, clicking Rollback sometimes shows a toast "rollback failed" (no overlay) and the version stays on the current release. Backups exist (e.g. 20251211-034204, 20251211-034350), and rollback succeeds when called directly via the API/CLI, so failure seems specific to the dashboard-triggered background job/overlay timing.

Steps observed

  1. Update to latest release from the dashboard (shows overlay).
  2. Refresh page.
  3. Click Rollback.
  4. Toast reports failure; version does not change.

Current behavior

  • UI sometimes reports rollback failed; version remains at 0.1.0-dev1.
  • /api/update/rollback via curl or CLI sometimes works, so it may be a transient/background job timing or UI poll issue.

Expected

  • Overlay shows during rollback, and system reverts to previous backup reliably.

Notes

  • Backups on device: 20251211-034204, 20251211-034350 (both version 0.1.0-dev).
  • PIKIT_MANIFEST_URL and PIKIT_AUTH_TOKEN are set via systemd override; update/download works.
  • Need to inspect systemd-run rollback unit and UI poll/overlay timing for race conditions.
**Problem** After updating to 0.1.0-dev1 via the dashboard, clicking Rollback sometimes shows a toast "rollback failed" (no overlay) and the version stays on the current release. Backups exist (e.g. 20251211-034204, 20251211-034350), and rollback succeeds when called directly via the API/CLI, so failure seems specific to the dashboard-triggered background job/overlay timing. **Steps observed** 1. Update to latest release from the dashboard (shows overlay). 2. Refresh page. 3. Click Rollback. 4. Toast reports failure; version does not change. **Current behavior** - UI sometimes reports rollback failed; version remains at 0.1.0-dev1. - /api/update/rollback via curl or CLI sometimes works, so it may be a transient/background job timing or UI poll issue. **Expected** - Overlay shows during rollback, and system reverts to previous backup reliably. **Notes** - Backups on device: 20251211-034204, 20251211-034350 (both version 0.1.0-dev). - PIKIT_MANIFEST_URL and PIKIT_AUTH_TOKEN are set via systemd override; update/download works. - Need to inspect systemd-run rollback unit and UI poll/overlay timing for race conditions.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
44r0n7
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: 44r0n7/pi-kit#1
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?