Hi everyone,
I'm experiencing this error on setting up my U-Boot based device:
Unable to extract cpio archive '/var/lib/lava/dispatcher/tmp/17/extract-overlay-ramdisk-tv17mriz/ramdisk.cpio': Command '['cpio', '--extract', '--make-directories', '--unconditional', '--file', '/var/lib/lava/dispatcher/tmp/17/extract-overlay-ramdisk-tv17mriz/ramdisk.cpio']' returned non-zero exit status 2.
As documentation in https://docs.lavasoftware.org/lava/actions-deploy.html#deploy-action-roles states, the overlay will only be used, when a test action is defined in job - so I removed the test action (and the log states "[common] skipped lava-overlay - no test action.") but the error still appears.
For debugging I commented out the _cleanup() function in /usr/lib/python3/dist-packages/lava_dispatcher/job.py (and can see in job output that dispatcher tmp directory isn't cleaned anymore) but somehow the directory still disappears, so I don't know how to debug this further.
So what's going wrong here? How to get the overlay working?
Running LAVA 2023.01 on Debian 11.6, full log see attached.
Thanks in advance!
Hi everyone!
Luckily problems solved!
As I wasn't able to preserve the temp directory from cleanup, I copied directory content to another directory before it was cleaned, and got it sorted out there: gpio call did some weird messages like
cpio: warning: skipped 44702 bytes of junk cpio: warning: archive header has reverse byte-order
But file itself was okay: # file ramdisk.cpio ramdisk.cpio: u-boot legacy uImage, , Linux/ARM, RAMDisk Image (gzip), 12579210 bytes, Thu Nov 3 10:07:07 2022, Load Address: 0x00000000, Entry Point: 0x00000000, Header CRC: 0x9708B60B, Data CRC: 0x1CD60EA6
Crucial point is that LAVA seemed to expect the Ramdisk without U-Boot header, but didn't check that either.
Luckily there's a configuration option (see https://validation.linaro.org/static/docs/v2/actions-deploy.html?highlight=r...) so that a Ramdisk with header gets accepted too:
ramdisk: url: https://file.local/uRamdisk compression: gz header: u-boot
As one can see in logs, header than gets removed automatically:
start: 1.4.3 extract-overlay-ramdisk (timeout 00:04:00) [common] dd if=/srv/tftp/26/tftp-deploy-klod5cyw/ramdisk/uRamdisk of=/var/lib/lava/dispatcher/tmp/26/extract-overlay-ramdisk-fdmylpik/ramdisk.cpio.gz ibs=64 skip=1
Done! Problem solved.
Stefan
On 3/17/2023 10:50 AM, Stefan wrote:
Hi everyone,
I'm experiencing this error on setting up my U-Boot based device:
Unable to extract cpio archive '/var/lib/lava/dispatcher/tmp/17/extract-overlay-ramdisk-tv17mriz/ramdisk.cpio': Command '['cpio', '--extract', '--make-directories', '--unconditional', '--file', '/var/lib/lava/dispatcher/tmp/17/extract-overlay-ramdisk-tv17mriz/ramdisk.cpio']' returned non-zero exit status 2.
As documentation in https://docs.lavasoftware.org/lava/actions-deploy.html#deploy-action-roles states, the overlay will only be used, when a test action is defined in job - so I removed the test action (and the log states "[common] skipped lava-overlay - no test action.") but the error still appears.
For debugging I commented out the _cleanup() function in /usr/lib/python3/dist-packages/lava_dispatcher/job.py (and can see in job output that dispatcher tmp directory isn't cleaned anymore) but somehow the directory still disappears, so I don't know how to debug this further.
So what's going wrong here? How to get the overlay working?
Running LAVA 2023.01 on Debian 11.6, full log see attached.
Thanks in advance!
lava-users@lists.lavasoftware.org
-
Stefan