There is a race when editing the /etc/fstab to add e.g. an entry for /boot (well any) fstab entry from the .wks into the filesystem image used for wic. This appears sporadically an has been bugging us with spurious broken images and bugreports for some time.

The issue surfaces as after do_image there is a parallel invocation of

1: agl-image-ivi-crosssdk-1.0-r0 do_image_tar - 25s (pid 14242)
2: agl-image-ivi-crosssdk-1.0-r0 do_image_wic - 24s (pid 14272)
3: agl-image-ivi-crosssdk-1.0-r0 do_image_ext4 - 25s (pid 14282)
 

Now the nasty issue is that do_image_wic will actually modify /etc/fstab.

So depending on how far the other 2 processes are, they get the modification or not.

This results in broken ext4 images (as there in no /boot to mount there).

Like:

A start job is running for /dev/disk/by-uuid/94E3-F144 (10s / 4mi 

Which is nonsense when using the ext4 under qemu.