OTA Error Code: deploy_firmware_artifact_prep_failed
Viewing this guide for
This alarm is covered by this guide. Background
Section titled “Background”This error can occur when the network connection does not allow the firmware build artifacts to be downloaded before a timeout.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
identify-jump-host-type{"<small><b>Step 1</b></small><br/>Question: Is the jump host a dock or smart cart?"}
check-dock-active-alarms["<small><b>Step 2</b></small><br/>Action: Go to the dock's FleetWrangler page a..."]
is-dock-internet-alarm-set{"<small><b>Step 3</b></small><br/>Question: Is the NO_INTERNET_VIA_ETHERNET or ..."}
follow-dock-network-alarm-guide["<small><b>Step 4</b></small><br/>Action: Follow the guide for the active alarm..."]
confirm-smart-cart-internet["<small><b>Step 5</b></small><br/>Action: Confirm that the smart cart has a hig..."]
retry-deploy-once["<small><b>Step 6</b></small><br/>Action: Retry deploying software once."]
was-redeploy-successful{"<small><b>Step 7</b></small><br/>Question: Was the redeploy successful?"}
deploy-succeeded["<small><b>Step 8</b></small><br/>Action: The problem is resolved; no further O..."]
escalate-to-ota-support{{"<small><b>Step 9</b></small><br/>Escalation: If you're a maintenance technician, e..."}}
identify-jump-host-type -->|Dock| check-dock-active-alarms
identify-jump-host-type -->|Smart Cart| confirm-smart-cart-internet
check-dock-active-alarms --> is-dock-internet-alarm-set
is-dock-internet-alarm-set -->|Yes| follow-dock-network-alarm-guide
is-dock-internet-alarm-set -->|No| retry-deploy-once
follow-dock-network-alarm-guide --> was-redeploy-successful
confirm-smart-cart-internet --> retry-deploy-once
retry-deploy-once --> was-redeploy-successful
was-redeploy-successful -->|Yes| deploy-succeeded
was-redeploy-successful -->|No| escalate-to-ota-support
style identify-jump-host-type fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style check-dock-active-alarms fill:#dcfce7,stroke:#22c55e,color:#14532d
style is-dock-internet-alarm-set fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style follow-dock-network-alarm-guide fill:#dcfce7,stroke:#22c55e,color:#14532d
style confirm-smart-cart-internet fill:#dcfce7,stroke:#22c55e,color:#14532d
style retry-deploy-once fill:#dcfce7,stroke:#22c55e,color:#14532d
style was-redeploy-successful fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style deploy-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
Is the jump host a dock or smart cart?
2 action
Go to the dock's FleetWrangler page and check the active alarms.
3 question
Is the
NO_INTERNET_VIA_ETHERNET or UNSTABLE_INTERNET_VIA_ETHERNET alarm set on the dock? 4 action
Follow the guide for the active alarm: NO_INTERNET_VIA_ETHERNET or UNSTABLE_INTERNET_VIA_ETHERNET. After the network alarm is resolved, retry deploying software.
If you are a maintenance technician, escalate to service engineering using an RFI to take over troubleshooting here.
If you are a maintenance technician, escalate to service engineering using an RFI to take over troubleshooting here.
5 action
Confirm that the smart cart has a high-bandwidth internet connection and that Wi-Fi is on. If SSH to the smart cart is failing, follow Smart Cart SSH Failure.
If you are a maintenance technician, escalate to service engineering using an RFI to take over troubleshooting here.
If you are a maintenance technician, escalate to service engineering using an RFI to take over troubleshooting here.
6 action
Retry deploying software once.
7 question
Was the redeploy successful?
8 action
The problem is resolved; no further OTA troubleshooting is needed for this error.
9 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.