"json:reporting" parameter for reporting type passed incorrectly, curtin fails to parse

[Harald Linden]

"INFO root:39 start: subiquity/Install/install/configure_apt: configuring apt"

...failed due to an error in the GPG-public-key passed in the autoinstall-config.

Subiquity then starts the same task a lot more verbose:

"DEBUG subiquitycore.utils:112 astart_command called: ['systemd-run', '--wait', '--same-dir', '--property', 'SyslogIdentifier=subiquity_log.2232', '--property', 'PrivateMounts=yes', '--setenv', 'PATH=/snap/subiquity/3698/bin:/snap/subiquity/3698/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/subiquity/3698/bin', '--setenv', 'PYTHONPATH=:/snap/subiquity/3698/lib/python3.8/site-packages', '--setenv', 'PYTHON=/snap/subiquity/3698/usr/bin/python3.8', '--setenv', 'SNAP=/snap/subiquity/3698', '--', '/snap/subiquity/3698/usr/bin/python3.8', '-m', 'curtin', '--showtrace', '-vvv', '--set', 'json:reporting={"subiquity": {"type": "journald", "identifier": "curtin_event.2232.1"}}', '-c', '/var/log/installer/subiquity-curtin-apt.conf', 'apt-config', '-t', '/tmp/tmp5qaoz6te/mount']"

curtin fails to parse the json for the reporting var correctly due to the whitespace inside and the lack of quotes outside, thus assuming '{"type' to be a subcmd.

"curtin: error: argument subcmd: invalid choice: '{type:' (choose from 'apply_net', 'apt-config', 'block-attach-iscsi', 'block-detach-[...]"

[Dan Bungert (dbungert)]

Thanks for the report Harold.

Would you provide a sample autoinstall file that shows this?

[Harald Linden (hlinden-gon)]

Here's an example. The public GPG-key in the extra sources section has a broken formatting. However, any error in the curtin apt section will trigger the bug as subiquity will try to restart curtin apt-config in verbose mode after it fails once.