OTA Error Code: deploy_install_job_failed
Viewing this guide for
Background
Section titled “Background”deploy_install_job_failed indicates that an OTA install job failed, timed out, or was rejected while deploying OS, apps, or firmware.
Install slowdowns and timed out streams are a common cause, but they are not the only cause of this error.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
is-this-curl-55-or-56{"<small><b>Step 1</b></small><br/>Question: In the failure summary on Slack, is ..."}
does-package-read-os{"<small><b>Step 2</b></small><br/>Question: Is package os? !Example Slack fa..."}
find-the-target-field["<small><b>Step 3</b></small><br/>Action: In the Slack message, find the targe..."]
what-is-the-target-field{"<small><b>Step 4</b></small><br/>Question: What is the 'target' field?"}
ssh-into-droid["<small><b>Step 5</b></small><br/>Action: SSH into the Droid. For steps, see S..."]
ssh-into-compute-a["<small><b>Step 6</b></small><br/>Action: SSH into compute A. For steps, see S..."]
ssh-into-compute-b["<small><b>Step 7</b></small><br/>Action: SSH into compute B. For steps, see S..."]
remove-corrupted-os-artifacts["<small><b>Step 8</b></small><br/>Action: Run sudo rm -rf /application/ota_out..."]
reattempt-ota["<small><b>Step 9</b></small><br/>Action: Reattempt OTA."]
was-ota-successful-after-removing-corrupted-os-artifacts{"<small><b>Step 10</b></small><br/>Question: Was OTA successful after removing cor..."}
ota-succeeded["<small><b>Step 11</b></small><br/>Action: No further OTA troubleshooting is nee..."]
escalate-to-ota-support{{"<small><b>Step 12</b></small><br/>Escalation: If you're a maintenance technician, e..."}}
is-this-curl-55-or-56 -->|No| escalate-to-ota-support
is-this-curl-55-or-56 -->|Yes| does-package-read-os
does-package-read-os -->|No| escalate-to-ota-support
does-package-read-os -->|Yes| find-the-target-field
find-the-target-field --> what-is-the-target-field
what-is-the-target-field -->|droid| ssh-into-droid
what-is-the-target-field -->|zip_a| ssh-into-compute-a
what-is-the-target-field -->|zip_b| ssh-into-compute-b
ssh-into-droid --> remove-corrupted-os-artifacts
ssh-into-compute-a --> remove-corrupted-os-artifacts
ssh-into-compute-b --> remove-corrupted-os-artifacts
remove-corrupted-os-artifacts --> reattempt-ota
reattempt-ota --> was-ota-successful-after-removing-corrupted-os-artifacts
was-ota-successful-after-removing-corrupted-os-artifacts -->|Yes| ota-succeeded
was-ota-successful-after-removing-corrupted-os-artifacts -->|No| escalate-to-ota-support
style is-this-curl-55-or-56 fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style does-package-read-os fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style find-the-target-field fill:#dcfce7,stroke:#22c55e,color:#14532d
style what-is-the-target-field fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style ssh-into-droid fill:#dcfce7,stroke:#22c55e,color:#14532d
style ssh-into-compute-a fill:#dcfce7,stroke:#22c55e,color:#14532d
style ssh-into-compute-b fill:#dcfce7,stroke:#22c55e,color:#14532d
style remove-corrupted-os-artifacts fill:#dcfce7,stroke:#22c55e,color:#14532d
style reattempt-ota fill:#dcfce7,stroke:#22c55e,color:#14532d
style was-ota-successful-after-removing-corrupted-os-artifacts fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style ota-succeeded fill:#dcfce7,stroke:#22c55e,color:#14532d
style escalate-to-ota-support fill:#fef3c7,stroke:#f59e0b,color:#78350f Hover or focus a block to preview it. Select the block to keep the preview open.
1 question
In the failure summary on Slack, is
updater_error exactly curl exit code, and is updater_message exactly Some(55) or Some(56)? 2 question
Is
package os? 3 action
In the Slack message, find the
target field. 4 question
What is the "target" field?
5 action
SSH into the Droid. For steps, see SSH into Droid.
6 action
SSH into compute A. For steps, see SSH into Compute A/B.
7 action
SSH into compute B. For steps, see SSH into Compute A/B.
8 action
Run
sudo rm -rf /application/ota_output/*.swu to remove potentially corrupted OS artifacts. 9 action
Reattempt OTA.
10 question
Was OTA successful after removing corrupted OS artifacts?
11 action
No further OTA troubleshooting is needed for this error.
12 escalation
If you're a maintenance technician, escalate to service engineering using an RFI. If you're a service engineer, escalate to OTA Support On Call.
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.