KIWI-NG build fails over checksum

English Applications
1

I am trying to build a ISO with kiwi-ng but I get checksum error.

kiwi-ng --debug --type iso system build --description ./descriptors/suse/x86_64/suse-leap-15.2 --target-dir /home/flux/.local/iso

Error -

 ERROR   ]: 22:43:01 | KiwiInstallPhaseFailed: System package installation failed: warning: Found NDB Packages.db database while attempting bdb backend: using ndb backend. 
warning: Found NDB Packages.db database while attempting bdb backend: using ndb backend. 
warning: Found NDB Packages.db database while attempting bdb backend: using ndb backend. 
Package libicu65_1-ledata-65.1-lp152.2.1.noarch (Leap-15.2_OSS) seems to be corrupted during transfer. Do you want to retry retrieval? 
Problem occurred during or after installation or removal of packages: 
Installation has been aborted as directed. 
Please see the above error message for a hint. 

 INFO    ]: 22:43:01 | Cleaning up SystemPrepare instance 
 DEBUG   ]: 22:43:01 | EXEC: [mountpoint -q /home/flux/.local/iso/build/image-root/var/cache/kiwi] 
 DEBUG   ]: 22:43:01 | EXEC: [mountpoint -q /home/flux/.local/iso/build/image-root/var/cache/kiwi] 
 DEBUG   ]: 22:43:01 | EXEC: [umount -l /home/flux/.local/iso/build/image-root/var/cache/kiwi] 
 DEBUG   ]: 22:43:01 | EXEC: [mountpoint -q /home/flux/.local/iso/build/image-root/sys] 
 DEBUG   ]: 22:43:01 | EXEC: [mountpoint -q /home/flux/.local/iso/build/image-root/sys] 
 DEBUG   ]: 22:43:01 | EXEC: [umount -l /home/flux/.local/iso/build/image-root/sys]

Is there a way for retry and/or change the checksum? I am testing kiwi-ng for the first time and not sure what needs to be done with it. Please help.

2

This issue is automatically fixed after the 5th attempt.

3

I would call that “automagically”. :wink:

4

Couldn’t agree more.

I built the ISO, booted off it. I am getting “can not open the console, root account is locked”, I will try to figure it out and if I can’t I will post a new thread.

5

From time to time I run into a similar problem scripting a package installation.
I’ve resolved by trying the following

  • Change the order of packages listed for installation
  • Install the package in a completely different part of the script (might require re-sequencing the script stanzas).

Not sure why this happens.
I’ve checked whether there can be a sequencing dependency, but have ruled this out every time (still should be re-checked every time).
It’s definitely not because of network issues largely because the problem is repeatable and the package eventually can be made to work (so there isn’t an actual corruption). This is based on a theory that there might be multiple threads downloading in parallel which have not completed.

TSU