Common-Torizon updates: 'Current versions in storage and reported by OSTree do not match'

[ToradexAI]

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

Did you like my answer?

---

Hello,

The error message ‘Current versions in storage and reported by OSTree do not match’ typically indicates a discrepancy between the version information stored in the device’s metadata and what OSTree reports. This can occur due to several reasons:

1. Incomplete Update Process: If an update was interrupted or not completed successfully, it might lead to such mismatches. Ensure that any updates are fully completed and that the device is not powered off during the process.

2. Manual Changes: If there were manual changes made to the OSTree repository or the file system, it could cause version mismatches. Verify that no unauthorized changes have been made.

3. Corrupted Metadata: Sometimes, the metadata used by OSTree or aktualizr can become corrupted. You might need to reset or reinitialize the OSTree repository to resolve this.

Regarding the error ‘FATAL: Program not found /usr/bin/fw_printenv’, this indicates that the fw_printenv utility, which is used to read environment variables from the U-Boot environment, is missing. This utility is crucial for certain operations, especially if your setup involves U-Boot. You can resolve this by installing the necessary package that provides fw_printenv.

For the error related to the action-handler returning an unexpected exit code, ensure that all scripts and handlers are correctly installed and configured. The exit code 113 might indicate a specific issue with the script or its environment.

To troubleshoot further:

• Check the logs for more detailed error messages that might provide additional context.
• Ensure that your Torizon setup is correctly configured for the intended use case, whether it’s for secure boot or updates.
• Verify that all necessary packages and dependencies are installed on your system.

I hope this helps resolve the issues you’re encountering. If you have any more questions, feel free to ask.

Best regards,
Toradex AI Assistant

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

Problem with Torizon OTA - no component to update

I’ve got problem connected with Torizon OTA – during upgrades via OTA something went wrong – upgrade got stuck, one day later after delete and added device again it passed (got successful message in terminal) , but at OTA webpage I can’t upgrade board - after update initiation I can’t select component to update – there are no option to select, as it was before. The screenshot showing the problem:

Torizon Platform update Error

I’ve followed the steps to update the dockercompose using TorizonOta, but the TorizonOta is presenting error and does not update the Toradex Verdin Imx8mm I’ve stopped all the containers through the command docker stop docker stop $(docker ps -a -q), then I’ve executed the steps below: I’ve add the toradex into TorizonOTA webpage I’ve used the default docker-compose-example-arm64 I’ve tried to update the Toradex, but no success. CONTAINER ID IMAGE COMMAN…

Upgrade python version in TorizonCore with yocto.