Hi James,
Thanks for your information. It's clear to me.
The cloud-init creates a distro-default user by default despite no user-data
configurations.
Only if no seed data exists, then cloud-init didn't run anything.
Move this case to invalid. Tks.
** Changed in: cloud-init (Ubuntu)
I believe that cloud-init is working as intended here. I'm unfamiliar
with the Ubuntu Image tool, but it looks like there is overlap between
the user-creation from that tool and cloud-init.
When cloud-init runs, it will by default create a distro-default user with no
password and password login
