REPROVISION_REQUIRED
Applicable alarms (1)
Likely outcomes — click to expand
Based on 0 missions where this alarm fired in the last 90 days as of 2026-10-13
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Background
Section titled “Background”This alarm means the hover configuration checker believes the hardware is physically installed in the expected locations, but the software identity or provisioning does not match the expected assignment.
This usually indicates a provisioning or role-information mismatch rather than a physical hardware swap.
See DISTRO HOVER CONFIGURATION CHECKER for a description of how the diagnostic works.
Troubleshooting Steps
Section titled “Troubleshooting Steps”Related pages
Section titled “Related pages”graph TD
is-draft-reprovision-required-active-o{"<small><b>Step 1</b></small><br/>Question: Is REPROVISION_REQUIRED active on ..."}
power-cycle-the-vehicle-and-send-a-pre{"<small><b>Step 2</b></small><br/>Question: Power cycle the vehicle and send a pr..."}
the-aircraft-may-return-to-service["<small><b>Step 3</b></small><br/>Action: The aircraft may return to service."]
run-an-ota-to-update-firmware-and-hov["<small><b>Step 4</b></small><br/>Action: Run an OTA to update firmware and hov..."]
send-a-preflight-mission-again-did-pre{"<small><b>Step 5</b></small><br/>Question: Send a preflight mission again. Did p..."}
the-aircraft-may-return-to-service-2["<small><b>Step 6</b></small><br/>Action: The aircraft may return to service."]
escalate-to-p2-firmware-motors-on-cal{{"<small><b>Step 7</b></small><br/>Escalation: Escalate to P2 Firmware Motors On Call."}}
continue-troubleshooting-using-the-ala["<small><b>Step 8</b></small><br/>Action: Continue troubleshooting using the al..."]
is-draft-reprovision-required-active-o -->|Yes| power-cycle-the-vehicle-and-send-a-pre
is-draft-reprovision-required-active-o -->|No| continue-troubleshooting-using-the-ala
power-cycle-the-vehicle-and-send-a-pre -->|Yes| the-aircraft-may-return-to-service
power-cycle-the-vehicle-and-send-a-pre -->|No| run-an-ota-to-update-firmware-and-hov
run-an-ota-to-update-firmware-and-hov --> send-a-preflight-mission-again-did-pre
send-a-preflight-mission-again-did-pre -->|Yes| the-aircraft-may-return-to-service-2
send-a-preflight-mission-again-did-pre -->|No| escalate-to-p2-firmware-motors-on-cal
style is-draft-reprovision-required-active-o fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style power-cycle-the-vehicle-and-send-a-pre fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style the-aircraft-may-return-to-service fill:#dcfce7,stroke:#22c55e,color:#14532d
style run-an-ota-to-update-firmware-and-hov fill:#dcfce7,stroke:#22c55e,color:#14532d
style send-a-preflight-mission-again-did-pre fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style the-aircraft-may-return-to-service-2 fill:#dcfce7,stroke:#22c55e,color:#14532d
style escalate-to-p2-firmware-motors-on-cal fill:#fef3c7,stroke:#f59e0b,color:#78350f
style continue-troubleshooting-using-the-ala fill:#dcfce7,stroke:#22c55e,color:#14532d Hover or focus a block to preview it. Select the block to keep the preview open.
REPROVISION_REQUIRED active on /distro_a.power_status?Resolution note
This plaintext block is ready to paste into the Resolution Note field on the ZERP issue you're working. The permalink below gives engineering review access to the full step-by-step timeline including any back-navigation; share it if the case needs a deeper look.
Permalink:
Session is too large to fit in a URL. Use Download session JSON to share the timeline out-of-band.
Did this guide help you get unblocked?
Open suggestions
There are no open suggestions.
Open pull requests
There are no open pull requests.