0x0010047E ZIP_EXECUTIVE_V4_COMPUTE_A_NOT_IN_FLIGHT_TARGET
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 Zip Executive alarm indicates Compute A was not in the flight systemd target when Zip Executive expected it.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
check-provisioning-agent-logs["<small><b>Step 1</b></small><br/>Action: SSH into the compute and look at the ..."]
does-log-show-max-backoff{"<small><b>Step 2</b></small><br/>Question: Do the logs show Max backoff reached?"}
check-mtls-cert-expiration["<small><b>Step 3</b></small><br/>Action: From /application/certs/provisioning..."]
is-cert-expired{"<small><b>Step 4</b></small><br/>Question: Is today's date past the Not After ..."}
send-reboot-mission["<small><b>Step 5</b></small><br/>Action: Send a reboot mission, then reattempt..."]
was-retry-successful{"<small><b>Step 6</b></small><br/>Question: Was the mission retry successful?"}
return-to-service["<small><b>Step 7</b></small><br/>Action: Return the Aircraft to service after ..."]
follow-the-guide-for-that-error["<small><b>Step 8</b></small><br/>Action: Follow the troubleshooting guide for ..."]
escalate-to-p2-exec{{"<small><b>Step 9</b></small><br/>Escalation: Escalate to P2 Exec On Call."}}
escalate-to-p2-embedded-platform{{"<small><b>Step 10</b></small><br/>Escalation: Escalate to P2 Embedded Platform On C..."}}
check-provisioning-agent-logs --> does-log-show-max-backoff
does-log-show-max-backoff -->|Yes| check-mtls-cert-expiration
does-log-show-max-backoff -->|No| send-reboot-mission
check-mtls-cert-expiration --> is-cert-expired
is-cert-expired -->|Yes| escalate-to-p2-embedded-platform
is-cert-expired -->|No| send-reboot-mission
send-reboot-mission --> was-retry-successful
was-retry-successful -->|Failed with the same error| escalate-to-p2-exec
was-retry-successful -->|Failed with a different error| follow-the-guide-for-that-error
was-retry-successful -->|Success| return-to-service
style check-provisioning-agent-logs fill:#dcfce7,stroke:#22c55e,color:#14532d
style does-log-show-max-backoff fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style check-mtls-cert-expiration fill:#dcfce7,stroke:#22c55e,color:#14532d
style is-cert-expired fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style send-reboot-mission fill:#dcfce7,stroke:#22c55e,color:#14532d
style was-retry-successful fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style return-to-service fill:#dcfce7,stroke:#22c55e,color:#14532d
style follow-the-guide-for-that-error fill:#dcfce7,stroke:#22c55e,color:#14532d
style escalate-to-p2-exec fill:#fef3c7,stroke:#f59e0b,color:#78350f
style escalate-to-p2-embedded-platform fill:#fef3c7,stroke:#f59e0b,color:#78350f Hover or focus a block to preview it. Select the block to keep the preview open.
journalctl logs for provisioning_agent with sudo journalctl -u provisioning_agent.service --no-pager | tail -n 20.Max backoff reached?/application/certs/provisioning, check the mTLS certificate validity with openssl x509 -in service-0_certificate.pem -text -noout | grep -A2 "Validity".Not After time on the certificate?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.