Do generic cloud images not use the local cloud-init data source?
I'm using the `virt-install --cloud-init` options:
```
virt-install
--cloud-init
meta-data="{{ CloudInitMetaDataFile.path }}",
user-data="{{ CloudInitUserDataTempFile.path }}",
network-config="{{ CloudInitNetworkConfigTempFile.path }}" \
```
I'm having an issue with the official generic cloud images available
from Debian, for example, `debian-12-genericcloud-amd64-daily-20241104-
1921.qcow2`.
The description for generic cloud says cloud-init is installed, but it
seems that these images are not applying the cloud-init settings, and
that results in an unusable VM as there are no accounts that can be
used to login.
The cloud-init file I'm passing in specifies accounts, but they aren't
being created.
I'm running this with an Ansible playbook, so it's highly repeatable.
When I tested the same playbook using a different image that I made
myself, the playbook works.
The image that I created myself was created with the FAI web tool,
selecting the "cloud" option, then adding the `cloud-init` package.
When running the playbook against the FAI+cloud-init image, it creates
the account, sets up the network, etc.
So there seems to be something wrong with the official generic cloud
images that causes them not to listen to settings coming from `virt-
install` via the `--cloud-init` options.
Any thoughts?
Nick
