This page describes how DPOD prepares the execution flow of a firmware upgrade plan (using tasks) and subsequently - how the tasks themselves are executed.
...
The Plan Details page shows the 40 most recent plan execution results,
The table outlines the following details for each plan execution
Column Name | Description |
|---|---|
| ID | The Plan Execution ID |
| Start Time | The time the plan entered the execution queue |
| Devices | Number of devices that were supposed to be upgraded. Both failed and successful upgrades are aggregated. |
| Status | The current status of the plan |
| Successful Tasks | Number of upgrade tasks that completed successfully for this plan execution |
| Failed Tasks | Number of upgrade tasks that failed for this plan execution |
| Skipped Tasks | Number of upgrade tasks that did not execute, e.g. because the device was not available |
| Error Message | Plan's Error message (If any) |
*Click the red "Abort Pending Executions" to stop execution in status "WAITING_FOR_PRE_VALIDATION" that did not started yet.
**Click the status column to drill into the activities execution details page.
Column Name | Description |
|---|---|
| ID | The Activity Execution ID |
| Status Time | The last time the status of the activity changed |
| Device Pattern | The device name or pattern that was used for this firmware upgrade activity |
| Firmware Image | The name of the image file selected for the upgrade |
| Status | The current status of the activity |
| Successful Tasks | Number of upgrade tasks that completed successfully for this activity execution |
| Failed Tasks | Number of upgrade tasks that failed for this activity execution |
| Skipped Tasks | Number of upgrade tasks that were skipped for this activity execution |
...