[3.0][bug] The seed configurations format wrong from 'cloud-init' function

[Laider Lai]

Hi,

The 'cloud-init' of the 'customization' function helps to create seed configurations at /var/lib/cloud/seed/nocloud.

But the format of generated configurations is wrong.
All configurations missing the configuration header '#cloud-config'.

This issue makes cloud-init skip seed configurations for deploying the system as expected.

[Reproduce steps]
1. Build an amd64 image with 'cloud-init' function. Ex. set up the user/password
2. Use QEMU to launch the image and use the expected user/password to login into the shell
3. Failed to login into the shell
4. Mount the rootfs partition of the image, checking mntimg/var/lib/cloud/instances/nocloud
5. The settings of cloud-config.txt is empty.

[Laider Lai (laiderlai)]

We remove cloud-init settings from the project yaml.
Then use a postscript to set cloud-init settings at first.
https://git.launchpad.net/~laiderlai/lyoncore/+git/iot-image-builds/commit/?id=53d4e8ff37dca9d3e3ee2c46a0ebcddcf1d7cd76

[Łukasz Zemczak (sil2100)]

This has been fixed when I was investigating this issue for the tegra images. The reference ubuntu-image image-definitions should now be correct: https://git.launchpad.net/ubuntu-images/tree/ubuntu-server-pc-amd64.yaml

[Laider Lai (laiderlai)]

Hi Lukasz,

Could you help to share the issue that is fixed by which version? Tks.

I tried again with ubuntu-image 3.0+snap10 version, but the configurations from var/lib/cloud/seed/nocloud are still missing the '#cloud-config' header.

[Laider Lai (laiderlai)]

Confirmed the issue is fixed with 3.0+snap12 rev577.
And the user-data yaml should add "#cloud-config" at the beginning.

Thank you.