OTA update doesn't complete from Torizon Cloud

Technical Support
, , , ,
2

Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!

Did you like my answer?

:+1: :-1:

The behavior you’re experiencing is likely due to the manual modification of the docker-compose.yaml file on the device. When you manually edit the docker-compose.yaml file in /var/sota/storage/docker-compose/, it can cause inconsistencies with the state expected by the Torizon OTA update system. Here’s a detailed explanation:

Why This Happens:

  1. State Mismatch: The Torizon OTA system, which uses Aktualizr and OSTree, maintains a specific state of the system and its components. When you manually change the docker-compose.yaml file, it creates a state that the OTA system does not recognize.
  2. Integrity Checks: The OTA system performs integrity checks to ensure that the updates are applied correctly and securely. Manual changes can cause these checks to fail or hang, as the system is trying to reconcile the expected state with the actual state.

Steps to Avoid This Issue:

  1. Avoid Manual Changes: Do not manually edit the docker-compose.yaml file directly on the device. Instead, make all changes through the Torizon Cloud interface or the appropriate OTA mechanisms.
  2. Revert Manual Changes: If you have already made manual changes, revert them to the original state before attempting another OTA update.

How to Recover:

  1. Revert to Original docker-compose.yaml: SSH into the device and revert the docker-compose.yaml file to its original state before the manual edit.
  2. Reboot the Device: Sometimes, a simple reboot can help the system to reinitialize and clear any temporary inconsistencies.
  3. Retry the OTA Update: Once the device is back to its expected state, retry the OTA update from Torizon Cloud.

Additional Recommendations:

  • Use TorizonCore Builder: For creating and managing custom docker-compose.yaml files, use TorizonCore Builder or the Torizon IDE extensions. This ensures that all changes are tracked and managed correctly.
  • Monitor Logs: Check the logs of Aktualizr and Docker to get more insights into what might be causing the update to hang. This can be done using commands like journalctl -u aktualizr and docker logs <container_id>.

If the issue persists even after following these steps, it might be worth reaching out to Toradex support with detailed logs and steps you have taken for further assistance.

Please, also check if these links can help you solve your problem:

Verdin iMX8M Plus - Mallow carrier board and 10 inch DSI display.