OTA Deployment Failures for Aircraft
Background
Section titled “Background”OTA failures can be caused by many reasons, from hardware failures up through site network issues. OTA client V2 introduces specific error codes to help direct the triage process. This is a landing page intended to point users to error code specific guides.
This guide is intended to be usable by both maintenance technicians and service engineers.
The error code guides use the term “jump host” to refer to the smart cart or dock that an aircraft is connected to. The jump host is necessary for the OTA system to connect to Zip. In FleetWrangler, the jump host is synonymous with the Dock ID field:
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
is-the-ota-failure-related-to-mission-persistence{"<small><b>Step 1</b></small><br/>Question: Is the OTA failure related to mission..."}
use-persistent-ota-mission-guide["<small><b>Step 2</b></small><br/>Action: Use the Persistent OTA Mission Issue..."]
see-this-slack-channel["<small><b>Step 3</b></small><br/>Action: See this Slack channelhttps://flyz..."]
find-the-error-code["<small><b>Step 4</b></small><br/>Action: Find the error code in the Slack mess..."]
if-the-ota-still-failed{{"<small><b>Step 5</b></small><br/>Escalation: If the OTA still failed, escalate. If..."}}
is-the-ota-failure-related-to-mission-persistence -->|Yes| use-persistent-ota-mission-guide
is-the-ota-failure-related-to-mission-persistence -->|No| see-this-slack-channel
see-this-slack-channel --> find-the-error-code
find-the-error-code --> if-the-ota-still-failed
style is-the-ota-failure-related-to-mission-persistence fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style use-persistent-ota-mission-guide fill:#dcfce7,stroke:#22c55e,color:#14532d
style see-this-slack-channel fill:#dcfce7,stroke:#22c55e,color:#14532d
style find-the-error-code fill:#dcfce7,stroke:#22c55e,color:#14532d
style if-the-ota-still-failed fill:#fef3c7,stroke:#f59e0b,color:#78350f Hover or focus a block to preview it. Select the block to keep the preview open.
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.
OTA V2 Error Codes
Section titled “OTA V2 Error Codes”- OTA Error Code: device_disk_space_preflight_failed
- OTA Error Code: deploy_firmware_artifact_prep_failed
- OTA Error Code: deploy_firmware_update_failed
- OTA Error Code: deploy_firmware_fw_update2_general_failure
- OTA Error Code: deploy_firmware_fw_update2_node_failure
- OTA Error Code: deploy_install_job_failed
- OTA Error Code: deploy_post_install_version_mismatch
- OTA Error Code: ssh_jump_host_unreachable
- OTA Error Code: ssh_name_resolution_failed
- OTA Error Code: ssh_target_channel_failure
Persistent OTA Mission Issues
Section titled “Persistent OTA Mission Issues”Did this guide help you get unblocked?
Open suggestions
Open pull requests
There are no open pull requests.