We write an empty /writable/system-data/etc/cloud directory into
the UC18 image. This means that the code that processes the
"transition" dirs assumes the content was already copied and skips
this dir. Using "synced" unbreaks things.
Once we have removed the creation of this dir during image bulding
we can revert this patch again.
This is actually more complicated and we may need to keep "synced"
because ubuntu-image provides a way to pass a cloud config file. However
if that file gets passed and is written the rest of the dir won't be synced
anymore (no ds-identify.cfg etc). So we need to think about this some more.
We write an empty /writable/system-data/etc/cloud directory into the UC18 image. This means that the code that processes the "transition" dirs assumes the content was already copied and skips this dir. Using "synced" unbreaks things.
Once we have removed the creation of this dir during image bulding we can revert this patch again.
This is actually more complicated and we may need to keep "synced" because ubuntu-image provides a way to pass a cloud config file. However if that file gets passed and is written the rest of the dir won't be synced anymore (no ds-identify.cfg etc). So we need to think about this some more.