Hardware Config Mismatch On Compute A and B
Background
Section titled “Background”This guide can be used to help triage cases when the hardware configuration file on compute A and compute B are mismatched.
There has been a recent regression in the OTA deployment software that can cause this alarm to falsely trigger if the device’s hardware configuration is mismatched on compute A and compute B.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
trigger-an-ota-to-current-version["<small><b>Step 1</b></small><br/>Action: Trigger an OTA to the Zip to the curr..."]
confirm-hardware-config-files-match-after-ota["<small><b>Step 2</b></small><br/>Action: After a successful OTA, confirm that ..."]
copy-compute-a-hardware-config-after-ota["<small><b>Step 3</b></small><br/>Action: Copy compute A's hardware config file..."]
copy-compute-b-hardware-config-after-ota["<small><b>Step 4</b></small><br/>Action: Copy compute B's hardware config file..."]
diff-the-hardware-config-files-after-ota["<small><b>Step 5</b></small><br/>Action: Diff the two hardware config files. R..."]
is-there-a-difference-after-ota{"<small><b>Step 6</b></small><br/>Question: Is there a difference between compute..."}
the-issue-is-resolved["<small><b>Step 7</b></small><br/>Action: The issue is resolved."]
escalate-to-p2-embedded-platform-on-call{{"<small><b>Step 8</b></small><br/>Escalation: The issue is persisting. Escalate to ..."}}
trigger-an-ota-to-current-version --> confirm-hardware-config-files-match-after-ota
confirm-hardware-config-files-match-after-ota --> copy-compute-a-hardware-config-after-ota
copy-compute-a-hardware-config-after-ota --> copy-compute-b-hardware-config-after-ota
copy-compute-b-hardware-config-after-ota --> diff-the-hardware-config-files-after-ota
diff-the-hardware-config-files-after-ota --> is-there-a-difference-after-ota
is-there-a-difference-after-ota -->|No| the-issue-is-resolved
is-there-a-difference-after-ota -->|Yes| escalate-to-p2-embedded-platform-on-call
style trigger-an-ota-to-current-version fill:#dcfce7,stroke:#22c55e,color:#14532d
style confirm-hardware-config-files-match-after-ota fill:#dcfce7,stroke:#22c55e,color:#14532d
style copy-compute-a-hardware-config-after-ota fill:#dcfce7,stroke:#22c55e,color:#14532d
style copy-compute-b-hardware-config-after-ota fill:#dcfce7,stroke:#22c55e,color:#14532d
style diff-the-hardware-config-files-after-ota fill:#dcfce7,stroke:#22c55e,color:#14532d
style is-there-a-difference-after-ota fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style the-issue-is-resolved fill:#dcfce7,stroke:#22c55e,color:#14532d
style escalate-to-p2-embedded-platform-on-call fill:#fef3c7,stroke:#f59e0b,color:#78350f Hover or focus a block to preview it. Select the block to keep the preview open.
scp zipline@[fe80::50%docklocal]:/config/hardware_config /tmp/hw_config.compute_a.scp zipline@[fe80::51%docklocal]:/config/hardware_config /tmp/hw_config.compute_b.diff -u /tmp/hw_config.compute_a /tmp/hw_config.compute_b. If there is output from the command, there is a difference between compute A and compute B's hardware config files.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.