Cloud-Init: can't login to newly created Debian 10 VM

[ivdok]

QEMU config:

agent: 1
balloon: 512
boot: dcn
bootdisk: scsi0
cipassword: plaintext-password # no different from hashed one
ciuser: root
cores: 20
cpu: host,flags=+pdpe1gb
cpuunits: 2048
ide2: local-zfs:vm-990-cloudinit,media=cdrom
ipconfig0: ip=10.0.0.2/8,gw=10.0.0.1
machine: q35
memory: 98304
name: builder
nameserver: 10.0.0.1
net0: virtio=3A:35:FE:FF:FF:FF,bridge=vmbr1
numa: 0
ostype: l26
scsi0: local-zfs:vm-990-disk-0,cache=writeback,size=32G
scsihw: virtio-scsi-pci
serial0: socket
smbios1: uuid=4313f3b7-3cf5-4d4c-9264-2abf242a72ab
sockets: 2
sshkeys: ssh-rsa-long-ass-key
vga: serial0
vmgenid: fd627870-6b9c-41a0-945b-155ea71c00be

PVE version:

proxmox-ve: 5.4-2 (running kernel: 4.15.18-17-pve)
pve-manager: 5.4-11 (running version: 5.4-11/6df3d8d0)
pve-kernel-4.15: 5.4-6
pve-kernel-4.15.18-18-pve: 4.15.18-44
pve-kernel-4.15.18-17-pve: 4.15.18-43
pve-kernel-4.15.18-16-pve: 4.15.18-41
pve-kernel-4.15.18-15-pve: 4.15.18-40
pve-kernel-4.15.18-14-pve: 4.15.18-39
pve-kernel-4.15.18-13-pve: 4.15.18-37
pve-kernel-4.15.18-12-pve: 4.15.18-36
pve-kernel-4.15.18-9-pve: 4.15.18-30
ceph: 12.2.12-pve1
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
gfs2-utils: 3.1.9-2
glusterfs-client: 6.4-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-12
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-53
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-14
libpve-storage-perl: 5.0-44
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-3
lxcfs: 3.0.3-pve1
novnc-pve: 1.0.0-3
proxmox-widget-toolkit: 1.0-28
pve-cluster: 5.0-37
pve-container: 2.0-39
pve-docs: 5.4-2
pve-edk2-firmware: 1.20190312-1
pve-firewall: 3.0-22
pve-firmware: 2.0-6
pve-ha-manager: 2.0-9
pve-i18n: 1.1-4
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 3.0.1-4
pve-xtermjs: 3.12.0-1
qemu-server: 5.0-54
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.13-pve1~bpo2

I've used OpenStack image from Debian repo, but for some reason I can't login at all - SSH is disabled, not installed or network is not working for some reason, and it doesn't accept my local credentials. What the hell? Cloud-Init used by Buster is newer that previous releases (18.3, definitely not "old and buggy" as @dcsapak mentioned for earlier images), and I've paid attention to use exactly controllers/drive names as in various examples. I've tried alternating between usernames and passwords, and regenerating cloud-init images, but to no avail.

 

[mira]

The link to the image does not work anymore. Did you get it to work?
I've tested the current one and it seems to work. (On an up-to-date PVE 6, though that should not make a difference in this case)

 

[ivdok]

No, I've McGyvered a solution using oem-config to do initial provisioning, since there was no hard requirement for Cloud-Init in the first place.