uc18 console-conf conflicts with cloud-init nocloud data source
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
subiquity |
New
|
Undecided
|
Unassigned |
Bug Description
If I use the following cloud-init user-data and meta-data with the nocloud data source:
user-data file:
#cloud-config
password: some-kind-
chpasswd: { expire: False }
ssh_pwauth: True
meta-data file:
instance-id: iid-local01
local-hostname: cloudimg
on my first boot of a uc18 image on a raspi4, then when snapd finishes seeding and hits console-conf, console-conf cannot continue to the "identity" page where I supply my email address because it complains thusly:
definition: eth0: 'set-name:' requires 'match:' properties\n
The full traceback from /var/log/
My expectation as a user is that since my cloud-init is quite simple, it would not interfere with any network related settings such that I could also use console-conf independently of my cloud-init.