Collecting the output for the failure would be useful. I don't know why
it returned 100 either. With the output that could be answered.
U-u is not designed to work in subiquity. If there is a design that
could be followed u-u could adjust the error codes, but in the current
form there are just too
Do you understand how unattended-upgrades could exit with code 100,
which is what happens in some error reports, e.g.
https://errors.ubuntu.com/oops/b3256088-6691-11ea-a143-fa163e6cac46. I
had a look and couldn't figure it out.
It doesn't seem quite right to me to ignore unattended-upgrade failure
IMO the exit of unattended-upgrade should be ignored in subiquity.
unattended-upgrades exits with 1 when it is interrupted and could stop
gracefully (subiquity user reboots before u-u could finish).
U-u also exits with error code when the archive contains an uninstallable
security update which th
** Summary changed:
-
/snap/subiquity/1459/usr/bin/subiquity:subprocess.CalledProcessError:_task_complete:result:__get_result:run:_bg_run_uu:_bg_run_command_logged:run_command:run
+ unattended-upgrades exiting with failure causes subiquity error
--
You received this bug notification because you
