dsidentify logs would be better, i think they are somewhere in /run/cloud* something directory.
Cause on boot ds-identify should run and determine the data sources.
Looking at your cmdline, it seems like ';' got interpreted as the end of string/command in uefi+grub2 boot
[ 0.000000] kernel: Command line: BOOT_IMAGE=/casper/vmlinuz quiet --- ds=nocloud-net
did you try to quote the ';' as in?
ds='nocloud-net;s=<url>' ? Is any shell scripts involved at all? maybe they are eating ';' too?
dsidentify logs would be better, i think they are somewhere in /run/cloud* something directory.
Cause on boot ds-identify should run and determine the data sources.
Looking at your cmdline, it seems like ';' got interpreted as the end of string/command in uefi+grub2 boot
[ 0.000000] kernel: Command line: BOOT_IMAGE= /casper/ vmlinuz quiet --- ds=nocloud-net
did you try to quote the ';' as in?
ds='nocloud- net;s=< url>' ? Is any shell scripts involved at all? maybe they are eating ';' too?