|
| 1 | +Upgrade Status Reference |
| 2 | +======================== |
| 3 | + |
| 4 | +.. contents:: **Table of contents**: |
| 5 | + :depth: 2 |
| 6 | + :local: |
| 7 | + |
| 8 | +Overview |
| 9 | +-------- |
| 10 | + |
| 11 | +OpenWISP Firmware Upgrader tracks the progress of firmware upgrade |
| 12 | +operations through different status values. Understanding these statuses |
| 13 | +is essential for monitoring upgrade operations and troubleshooting issues. |
| 14 | + |
| 15 | +In Progress |
| 16 | +~~~~~~~~~~~ |
| 17 | + |
| 18 | +**Status**: ``in-progress`` |
| 19 | + |
| 20 | +**Description**: The upgrade operation is currently running. This includes |
| 21 | +all phases of the upgrade process: device connection, firmware validation, |
| 22 | +file upload, and firmware flashing. |
| 23 | + |
| 24 | +**What happens during this status:** |
| 25 | + |
| 26 | +- Device identity verification |
| 27 | +- Firmware image validation |
| 28 | +- Some non-critical services may be stopped to free up memory, if needed |
| 29 | +- Image upload to the device |
| 30 | +- Firmware flashing process |
| 31 | + |
| 32 | +**User Actions**: Users can cancel upgrade operations that are in |
| 33 | +progress, but only before the firmware flashing phase begins (typically |
| 34 | +when progress is below 60%). |
| 35 | + |
| 36 | +Success |
| 37 | +~~~~~~~ |
| 38 | + |
| 39 | +**Status**: ``success`` |
| 40 | + |
| 41 | +**Description**: The firmware upgrade completed successfully. The device |
| 42 | +has been upgraded to the new firmware version and is functioning properly. |
| 43 | + |
| 44 | +**What this means:** |
| 45 | + |
| 46 | +- The firmware was successfully flashed to the device |
| 47 | +- The device rebooted with the new firmware |
| 48 | +- Connectivity was restored after the upgrade |
| 49 | +- All verification checks passed |
| 50 | + |
| 51 | +**Next Steps**: No action required. The upgrade is complete and the device |
| 52 | +is running the new firmware. |
| 53 | + |
| 54 | +Failed |
| 55 | +~~~~~~ |
| 56 | + |
| 57 | +**Status**: ``failed`` |
| 58 | + |
| 59 | +**Description**: The upgrade operation completed, but the system could not |
| 60 | +reach the device again after the upgrade. |
| 61 | + |
| 62 | +**Common causes:** |
| 63 | + |
| 64 | +- Hardware failures |
| 65 | +- Unexpected system errors |
| 66 | +- The network became unreachable after flashing the new firmware |
| 67 | + |
| 68 | +**Recommended Actions**: |
| 69 | + |
| 70 | +- Check network connectivity |
| 71 | +- Physical inspection and/or serial console debugging |
| 72 | + |
| 73 | +Aborted |
| 74 | +~~~~~~~ |
| 75 | + |
| 76 | +**Status**: ``aborted`` |
| 77 | + |
| 78 | +**Description**: The upgrade operation was stopped due to pre-requisites |
| 79 | +not being met. The system determined it was unsafe or impossible to |
| 80 | +proceed with the upgrade. |
| 81 | + |
| 82 | +**Common causes:** |
| 83 | + |
| 84 | +- Device UUID mismatch (wrong device targeted) |
| 85 | +- Insufficient memory on the device |
| 86 | +- Invalid or corrupted firmware image |
| 87 | + |
| 88 | +**What happens when aborted:** |
| 89 | + |
| 90 | +- The upgrade stops immediately |
| 91 | +- If services were stopped to free up memory, they are automatically |
| 92 | + restarted |
| 93 | +- No firmware changes are made to the device |
| 94 | +- Device remains in its original state |
| 95 | + |
| 96 | +**Recommended Actions**: |
| 97 | + |
| 98 | +- Verify the correct device is selected |
| 99 | +- Check firmware image compatibility |
| 100 | +- Ensure device has sufficient memory |
| 101 | + |
| 102 | +Cancelled |
| 103 | +~~~~~~~~~ |
| 104 | + |
| 105 | +**Status**: ``cancelled`` |
| 106 | + |
| 107 | +**Description**: The upgrade operation was manually stopped by the user |
| 108 | +before completion. This is a deliberate action taken through the admin |
| 109 | +interface or REST API. |
| 110 | + |
| 111 | +Users can cancel upgrades through the admin interface using the "Cancel" |
| 112 | +button that appears next to in-progress operations. |
| 113 | + |
| 114 | +**When cancellation is possible:** |
| 115 | + |
| 116 | +- During the early stages of upgrade (typically before 60% progress) |
| 117 | +- Before the new firmware image is written to the flash memory of the |
| 118 | + network device |
| 119 | +- While the operation status is still "in-progress" |
| 120 | + |
| 121 | +**What happens when the upgrade operation cancels:** |
| 122 | + |
| 123 | +- The upgrade process stops immediately |
| 124 | +- If services were stopped during the upgrade, they are automatically |
| 125 | + restarted |
| 126 | +- No firmware changes are made to the device |
| 127 | +- Device remains in its original state |
| 128 | + |
| 129 | +Status Flow |
| 130 | +----------- |
| 131 | + |
| 132 | +The typical flow of upgrade statuses follows this pattern: |
| 133 | + |
| 134 | +.. code-block:: none |
| 135 | +
|
| 136 | + in-progress → success |
| 137 | + ↓ |
| 138 | + failed/aborted/cancelled |
| 139 | +
|
| 140 | +**Typical successful upgrade:** |
| 141 | + |
| 142 | +1. ``in-progress`` |
| 143 | +2. ``success`` |
| 144 | + |
| 145 | +**Typical problematic upgrade:** |
| 146 | + |
| 147 | +1. ``in-progress`` 3. ``failed``: an unexpected error occurs during |
| 148 | +upgrade 2. **OR** ``aborted``: the system detects pre-condition failure |
| 149 | +and stops safely 4. **OR** ``cancelled``: the user manually stops the |
| 150 | +upgrade |
| 151 | + |
| 152 | +Monitoring Upgrades |
| 153 | +------------------- |
| 154 | + |
| 155 | +**Real-time Progress**: The admin interface provides real-time updates of |
| 156 | +upgrade operations, including progress percentages and detailed logs. |
| 157 | + |
| 158 | +**Upgrade Logs**: Each status change is logged with detailed information |
| 159 | +about what occurred during the upgrade process. |
| 160 | + |
| 161 | +**Batch Operations**: When performing mass upgrades, you can monitor the |
| 162 | +status of individual device upgrades within the batch operation. |
0 commit comments