As per discourse it looks like the bug is in Curtin.
/etc/cloud/cloud.cfg.d/90_dpkg_maas.cfg is written then deleted by
Curtin.
Applying debconf selections
Running command ['unshare', '--fork', '--pid', '--', 'chroot',
'/tmp/tmpihv32ogj/target', 'debconf-set-selections'] with allowed return codes
[0] (capture=True)
Running command ['unshare', '--fork', '--pid', '--', 'chroot',
'/tmp/tmpihv32ogj/target', 'dpkg-query', '--list'] with allowed return codes
[0] (capture=True)
unconfiguring cloud-init
cleaning cloud-init config from:
['/tmp/tmpihv32ogj/target/etc/cloud/cloud.cfg.d/90_dpkg_local_cloud_config.cfg',
'/tmp/tmpihv32ogj/target/etc/cloud/cloud.cfg.d/90_dpkg_maas.cfg',
'/tmp/tmpihv32ogj/target/etc/cloud/cloud.cfg.d/90_dpkg.cfg']
** Also affects: curtin
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1927020
Title:
cloudconfig not writing maas data source
Status in cloud-init:
Incomplete
Status in curtin:
New
Bug description:
further background https://discourse.maas.io/t/debian10-fails-on-
final-reboot/4486
I'm deploying a debian 10 buster image using MAAS. No errors are
reported in MAAS or curtin install but on the final boot cloud-init
reports `Failed to load metadata and userdata`. checking the config
for the machine in maas shows all the cloudconfig: to connect to maas
but the files with oauth credentials etc dont seem to have been copied
to the target.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1927020/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
