Failure to generate a lockbox

Technical Support
, , ,
1

Hi,

I’ve just created a new lockbox in Torizon Cloud and I am unable to create an offline image from it using torizoncore-builder 3.11.0.

I get the same error message if I request one of the lockboxes I created on Friday, which did not happen then.

Here is the output from the “platform lockbox” command:

torizoncore-builder platform lockbox --credentials credentials.zip --login-to <private registry> <user> <pwd> --output-directory ./build/lockbox/update/ <lockbox name>

=>> Handle director-repository metadata
Fetching 'kt-pxie-506-1_2_0.json'
Fetching 'offline-snapshot.json'
Fetching '1.root.json'
Fetching '2.root.json'
Fetching '3.root.json'
Fetching '3.root.json' (version not available, stopping)

=>> Handle image-repository metadata
Fetching 'snapshot.json'
Fetching 'targets.json'
Fetching 'tdx-containers.json'
Removing output directory './build/lockbox/update/' due to errors
Downloaded file 'tdx-containers.json' has wrong length (actual=92636, expected=92609 bytes)
1 Like
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:

Hello,

I’m sorry to hear you’re having trouble generating a lockbox with TorizonCore Builder 3.11.0. The error messages you provided suggest issues with metadata fetching and file integrity. Here are some steps to help resolve these issues:

  1. Verify File Integrity: The error indicates a mismatch in the expected and actual file length for ‘tdx-containers.json’. Try re-downloading this file to ensure it is not corrupted. A stable network connection is crucial to prevent incomplete downloads.

  2. Check for Software Updates: Ensure you are using the latest version of TorizonCore Builder. Updates may contain fixes for issues like the one you’re experiencing. If a newer version is available, consider upgrading.

  3. Review Logs for Details: Examine any additional logs generated by TorizonCore Builder for more detailed error messages. These logs can provide further insight into the issue.

  4. Network Stability: Ensure your network connection is stable during the download process to avoid file corruption.

If these steps do not resolve the issue, you might want to try the process on a different machine or environment to determine if the problem is specific to your current setup.

I hope this helps you resolve the issue. 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:

Offline updates not searching for lockbox.

3

I’m having the same issue when trying to push images to Torizon Cloud

1 Like
4

Update - I have been able to replicate the issue in the office today on the same laptop. So it does not appear to be a network stability issue.

5

I’m seeing the same issue today too.

1 Like
6

We are encountering the same error from our CI/CD-Pipelines (or using TCB manually) when trying to push images to Torizon Platform:

Downloaded file 'tdx-containers.json' has wrong length (actual=92636, expected=92609 bytes)

Maybe @drew.tx, you can help us, please?

Thank you very much.

Regards,
Lasse

7

Having the same issue as well

8

Hi all,

Thanks for reporting this. Our team is on it and I will report back when I get something concrete.

Drew

1 Like
9

Hi all, we are evaluating a fix for this issue.

If you refresh the tdx-containers package feed and generate a new lockbox this should work.

Does someone mind verifying this? It’s difficult for us to verify internally since it’s potentially different if aktualizr has recently (before this fix) seen an offline update.

10

I am still seeing the response:
Downloaded file ‘tdx-containers.json’ has wrong length (actual=92636, expected=92609 bytes)

,when trying to run a platform push.

Is this possibly a different issue?

11

To be clear, did you first refresh the tdx-containers package in the ui?

image
image711×594 42.9 KB

And then hit refresh:

image
image684×455 25.1 KB

?

2 Likes
12

Nope, sorry I missed that.

After refreshing them I am getting successful pushes, thank you!

13

No worries. It’s an odd thing to do for offline updates… i think we should add a call in tcb to refresh this on behalf of users so doing it manually isn’t necessary.

And sorry this was broken! Thank you for reporting and verifying

14

After doing the refresh manually, everything is working fine again.
Thank you for the fast response.

16

Thanks @kildea75 and @lbruhn-cw for checking and reporting back!

I would like to request @nclark, @i.staehli, @jonmills and @stasgil to also check and report back if this is either solved or something is still going wrong.

Best regards,

17

Solved for me, although I didn’t have permissions to refresh the package sources (as I’m not the primary account holder). My colleague was able to refresh it for me, and then I was able to push successfully.

I like @ben.tx 's suggestion to include this in TCB, given that in our use-case we rarely push via the front-end UI, so the solution wasn’t at all intuitive.

1 Like
18

I hijacked this thread a little bit, as i saw this issue when just pushing a package using torizoncore builder (no lockbox).
The issue has been resolved for me as well.
I didnt need to refresh anything ( we created our custom package source, which doesnt seem to have that option).

Thanks!

1 Like
19

@henrique.tx The issue of uploading to Torizon Cloud is solved for me. I didn’t have to refresh anything.

1 Like
20

Apologies for the delay in reporting back, the issue is resolved for me too. Thanks!

1 Like
21

Thank you all for the feedback!

Solved 7 out of 7. Nice score! :smiley:

Have a nice day!